Methods, apparatus, and systems for generating a corrective pickup notification for a shipped item based upon an intended pickup master node

ABSTRACT

A mobile master node apparatus is described for generating a corrective pickup notification related to an item being shipped based upon an intended pickup master node. The master node includes a processor, memory storage, location circuitry, and a communication interface. In operation, the mobile master node is unconventionally transformed to identify a location of the ID node; determine whether the location of the ID node and a detected location of the mobile master node indicates the item accompanies the mobile master node as it moves from a first location to a second location; identify an intended pickup master node from received shipping information related to the item; automatically sense an adverse pickup condition related to the item based upon the intended pickup master node and whether the item is accompanying the mobile master node; and generate the corrective pickup notification based upon the adverse pickup condition sensed.

The present application hereby claims the benefit of priority to relatedProvisional Patent Application No. 62/113,923 and entitled “Methods,Apparatus, and Systems for Enhanced Delivery and Pickup Management ofItems Using Elements of a Wireless Node Network.”

The present application is also related in subject matter to thefollowing non-provisional patent applications where each also claims thebenefit of priority to the same above-referenced provisional patentapplication: (1) Non-Provisional patent application Ser. No. ______,entitled “Enhanced Delivery Management Methods, Apparatus, and Systemsfor a Shipped Item using a Mobile Nod-enabled Logistics Receptacle”; (2)Non-Provisional patent application Ser. No. ______, entitled “ImprovedMethods, Apparatus, and Systems for Generating a Corrective PickupNotification for a Shipped Item Using a Mobile Master Node”; (3)Non-Provisional patent application Ser. No. ______, entitled “ImprovedMethods, Apparatus, and Systems for Transmitting a Corrective PickupNotification for a Shipped Item to a Courier Master Node”; (4)Non-Provisional patent application Ser. No. ______, entitled “ImprovedMethods, Apparatus, and Systems for Transmitting a Corrective PickupNotification for a Shipped Item Accompanying an ID Node Moving With aCourier Away from a Master Node”; (5) Non-Provisional patent applicationSer. No. ______, entitled “Improved Methods, Apparatus, and Systems forTransmitting a Corrective Pickup Notification for a Shipped ItemAccompanying an ID Node Based Upon Intended Pickup Master NodeMovement”; and (6) Non-Provisional patent application Ser. No. ______,entitled “Improved Methods, Apparatus, and Systems for Transmitting aGenerating a Pickup Notification Related to an Inventory Item.”

FIELD OF THE DISCLOSURE

The present disclosure generally relates to systems, apparatus andmethods in the field of tracking items (e.g., an object, a package, aperson, a piece of equipment) and, more particularly, to various aspectsinvolving systems, apparatus and methods for enhanced delivery and/orpickup management of an item using one or more elements of an adaptive,context-aware wireless node network as it relates to selective releaseof the item, corrective delivery/pickup notifications for an item, andpickup notifications related to an inventory item.

BACKGROUND

Asset management has always been an important part of commerce, and theability to identify an item and locate its whereabouts may be consideredcore to companies that ship items from one location to another. Forexample, tracking packages is important to organizations of all kinds,whether it be a company keeping track of inventory to be sold in itsstores, or a package delivery provider keeping track of packages beingtransported through its delivery network. To provide quality service, anorganization typically creates and maintains a highly organized networkfor tracking its items—packages, people, objects, etc. Effectivemanagement of such networks allows lower cost, reduced delivery time,and enhanced customer service. And efficient deployment of the networkhelps manage costs.

In addition to tracking packages, parties that ship and receive packagesmay also need information regarding the conditions of the packages, suchas the temperature and humidity of the package. For example, a customerthat has ordered a box of wine may want to monitor the temperature ofthe contents of the box to determine if the temperature and/or humiditygoes above or below a set range. Likewise, the party that ships thepackage may also want to monitor the conditions of the package to ensurethat the content arrives in the proper condition.

Conventionally, this tracking function may be provided by a variety ofknown mechanisms and systems. Machine-readable barcodes are one wayorganizations keep track of items. A retailer, for example, may use barcodes on items in its inventory. For example, items to be sold in aretailer's store may each be labeled with a different machine-readablebar code. In order to keep track of inventory, the retailer typicallyscans or otherwise captures an image of the bar code on each item sothat a back-end part of the retailer's operation can keep track of whatis coming in and leaving their possession from suppliers. In addition,when an item is sold to a consumer, the bar code for that item isscanned or captured to track sales and inventory levels.

Similarly, a package delivery provider may utilize machine-readable barcodes by associating a bar code with packages to be delivered to arecipient. For example, a package may have a bar code corresponding to atracking number for that package. Each time the package goes through atransit checkpoint (e.g., the courier taking initial control of thepackage, the package being temporarily placed in a storage facilitywhile being moved from a pickup point to a delivery location, and thepackage being delivered to the recipient, etc.), the package's bar codemay be scanned. Bar codes, however, have the disadvantage that personnelmust manually scan each bar code on each item in order to effectivelytrack the items.

Radio-frequency identification (RFID) tags are another known mechanismfor tracking items. In contrast to barcodes, RFID tags do not usuallyrequire manual scanning. For example, in a retail context, an RFID tagon an inventory item may be able to communicate with an electronicreader that detects items in a shopping cart and adds the cost of eachitem to a bill for the consumer. The RFID tag usually transfers a codednumber when queried or prompted by the reader. RFID tags have also beenused to track items such as livestock, railroad cars, trucks, and evenairline baggage. These tags typically only allow for basic tracking, butdo not provide a way to improve asset management using information aboutthe environment in which the items are tracked.

Sensor-based tracking systems are also known which can provide moreinformation than RFID systems. Shippers, carriers, recipients, and otherparties often wish to know the location, condition, and integrity ofshipments before, during, and after transport to satisfy quality controlgoals, meet regulatory requirements, and optimize business processes.However, such systems are typically expensive given the complexity ofthe sensors, and may provide extraneous and redundant item information.

Further problems exist with managing delivery of an item to help ensurethe item is delivered to the appropriate destination. For example, attimes, a courier may gather an item from a logistics receptacle (e.g., astorage area on a delivery van) and unintentionally drop off the item ata location that is not the intended delivery location for the item.Delivery restrictions, requirements, and conditions may inadvertently beviolated or unintentionally disregarded at times leading to potentialloss of the item for the recipient and/or costs related to replacing theitem or making a lengthy special trip to correct the delivery issue longafter the issue arose.

To address these requirements, a system is needed that may monitor dataregarding objects (such as shipped items, personnel, or equipment) andefficiently extend visibility of such objects as well as managelogistics operations based on monitoring objects and enhance how otherlogistics elements operate in response. Thus, there remains a need foran improved system that may provide more extensive and robustidentification, tracking, and management of objects and do so in a costeffective manner.

SUMMARY

In the following description, certain aspects and embodiments aregenerally directed to providing a technical solution for a logisticsmonitoring operation that generates a corrective pickup notificationrelated to an item being shipped (such as a package or other objectbeing transported between different locations) based upon an intendedpickup master node and location-based operations of a mobile master nodethat uses onboard hardware and executing programmatic code toautomatically sense an issue with delivery of the item being shipped. Itshould be understood that the aspects and embodiments, in their broadestsense, could be practiced without having one or more features of theseaspects and embodiments as described in more detail below. It shouldalso be understood that these aspects and embodiments are merelyexemplary.

For example, one aspect of the disclosure focuses on an improvedlocation-based method for generating a corrective pickup notificationrelated to an item being shipped based upon an intended pickup masternode. In general, the method has a mobile master node identifying alocation of an ID node associated with the item and detecting thecurrent location of the mobile master node. The method then has themobile master node determining whether the location of the ID nodeindicates the item is accompanying the mobile master node as the mobilemaster node moves from a first location to a second location. The methodthen has the mobile master node receiving shipping information relatedto the item and identifying the intended pickup master node from theshipping information. Then method proceeds with the mobile master nodeautomatically sensing an adverse pickup condition related to the itembased upon the identified intended pickup master node and thelocation-based determination of whether the location of the ID nodeindicates the item is accompanying the mobile master node. The methodthen has the mobile master node generating the corrective pickupnotification based upon the adverse pickup condition sensed.

In another aspect of the disclosure, a mobile master node is describedas a type of apparatus for generating a corrective pickup notificationrelated to an item being shipped based upon an intended pickup master.In general, the mobile master node apparatus includes at least a nodeprocessing unit, a node memory storage, location circuitry that detectsa current location of the mobile master node apparatus, and acommunication interface that provides access to a wireless communicationpath connecting the mobile master node apparatus with at least an IDnode associated with the item being shipped. Each of the node memorystorage, location circuitry, and communication interface are operativelycoupled to the programmable node processing unit. The node memorystorage maintains delivery notification code for execution by the nodeprocessing unit. When executing such code, the node processing unit isprogrammatically transformed and configured to become unconventionallyoperative to identify a location of the ID node associated with theitem; determine whether the identified location of the ID node and thedetected current location of the mobile master node apparatus indicatesthe item is accompanying the mobile master node apparatus as the mobilemaster node apparatus moves from a first location to a second location;receive shipping information related to the item; identify the intendedpickup master node from the shipping information; automatically sense anadverse pickup condition related to the item based upon the identifiedintended pickup master node and whether the location of the ID nodeindicates the item is accompanying the mobile master node apparatus; andgenerate the corrective pickup notification based upon the adversepickup condition sensed.

In still another aspect of the disclosure, an improved location-basedsystem is described for generating a corrective pickup notificationrelated to an item being shipped based upon an intended pickup masternode. Such a system generally includes at least a logistics server and amobile master node in communication with the logistics server. In moredetail, the logistics server is deployed in the system as maintaining acopy of shipping information related to the item being shipped and an IDnode associated with the item being shipped. The mobile master node incommunication with the logistics server is also in communication withthe ID node associated with the item being shipped. The mobile masternode comprises at least a node processing unit along with a node memorystorage, location circuitry, and two different communication interfaces.Each of the node memory storage, location circuitry, and two differentcommunication interfaces are operatively coupled to the node processingunit. The node memory storage operates to maintain delivery notificationcode for execution by the node processing unit. The location circuitryworks to detect a current location of the mobile master node and providesuch location information to the node processing unit. A first of thecommunication interfaces operates as part of the system's mobile masternode to access a first wireless communication path connecting the mobilemaster node with at least the ID node associated with the item beingshipped. The second communication interface is operative to access asecond wireless communication path connecting the mobile master nodewith the logistics server such that the first wireless communicationpath (e.g., a low energy Bluetooth® formatted wireless path) isdifferent and distinct from the second wireless communication path(e.g., a cellular or Wi-Fi formatted wireless path). When the nodeprocessing unit of the system's mobile master node executes the deliverynotification code, the node processing unit becomes unconventionallyoperative as part of the system to identify a location of the ID nodeassociated with the item being shipped; determine whether the identifiedlocation of the ID node and the detected current location of the mobilemaster node remain within a threshold distance from each other toindicate the item is accompanying the mobile master node as the mobilemaster node moves from a first location to a second location; receiveshipping information related to the item from the logistics server;identify the intended pickup master node from the received shippinginformation; automatically sense an adverse pickup condition related tothe item based upon the identified intended pickup master node andwhether the location of the ID node and the detected location of themobile master node indicates the item is accompanying the mobile masternode; and generate the corrective pickup notification based upon theadverse pickup condition sensed.

Each of these aspects respectively effect improvements to the technologyof tracked and monitored items that require delivery and enhancements tobetter identify delivery issues and proactively avoid delivery issues.Additional advantages of this and other aspects of the disclosedembodiments and examples will be set forth in part in the descriptionwhich follows, and in part will be obvious from the description, or maybe learned by practice of the invention. It is to be understood thatboth the foregoing general description and the following detaileddescription are exemplary and explanatory only and are not restrictiveof the invention, as claimed.

BRIEF DESCRIPTION OF THE DRAWINGS

The accompanying drawings, which are incorporated in and constitute apart of this specification, illustrate several embodiments according toone or more principles of the invention and together with thedescription, serve to explain one or more principles of the invention.In the drawings,

FIG. 1 is a diagram of an exemplary wireless node network in accordancewith an embodiment of the invention;

FIG. 2 is a more detailed diagram of an exemplary wireless node networkin accordance with an embodiment of the invention;

FIG. 3 is a more detailed diagram of an exemplary ID node device inaccordance with an embodiment of the invention;

FIG. 4 is a more detailed diagram of an exemplary master node device inaccordance with an embodiment of the invention;

FIG. 5 is a more detailed diagram of an exemplary server in accordancewith an embodiment of the invention;

FIG. 6 is a diagram illustrating the structure or format of an exemplaryadvertisement data packet in accordance with an embodiment of theinvention;

FIG. 7 is a diagram illustrating sample content for an exemplaryadvertisement data packet in accordance with an embodiment of theinvention;

FIG. 8 is a state diagram illustrating exemplary states and transitionsbetween the states as part of operations by an exemplary node in awireless node network in accordance with an embodiment of the invention;

FIG. 9 is a diagram illustrating exemplary components of a wireless nodenetwork during an exemplary master-to-ID node association in accordancewith an embodiment of the invention;

FIG. 10 is a diagram illustrating exemplary components of a wirelessnode network during an exemplary ID-to-ID node association in accordancewith an embodiment of the invention;

FIG. 11 is a diagram illustrating exemplary components of a wirelessnode network during an exemplary ID-to-master node query in accordancewith an embodiment of the invention;

FIG. 12 is a diagram illustrating exemplary components of a wirelessnode network during an exemplary alert advertising mode in accordancewith an embodiment of the invention;

FIG. 13 is a diagram illustrating an exemplary location determinationusing master node advertise in accordance with an embodiment of theinvention;

FIG. 14 is a diagram illustrating an exemplary location determinationusing ID node advertise in accordance with an embodiment of theinvention;

FIG. 15 is a diagram illustrating an exemplary location determinationthrough triangulation in accordance with an embodiment of the invention;

FIG. 16 is a diagram illustrating an exemplary location determinationthrough chaining triangulation in accordance with an embodiment of theinvention;

FIG. 17 is a diagram illustrating an example logistics operation usingexemplary components of a wireless node network in accordance with anembodiment of the invention;

FIG. 18 is a flow diagram illustrating an example method for managingshipment of an item using a wireless node network in accordance with anembodiment of the invention;

FIG. 19 is a flow diagram illustrating another example method formanaging shipment of an item using a wireless node network in accordancewith an embodiment of the invention;

FIG. 20 is a diagram illustrating exemplary node packages located in anexemplary vehicle environment in accordance with an embodiment of theinvention;

FIG. 21 is a diagram illustrating exemplary mobile storage units, suchas ULDs, used as containers that help ship node packages in an exemplaryairborne environment in accordance with an embodiment of the invention;

FIGS. 22A-22C are diagrams illustrating exemplary stages of an ID nodemoving through part of an exemplary transit path while associating withdifferent master nodes in accordance with an embodiment of theinvention;

FIG. 23 is a flow diagram illustrating an example method for associationmanagement of a wireless node network in accordance with an embodimentof the invention;

FIG. 24 is a flow diagram illustrating another example method forassociation management of a wireless node network in accordance with anembodiment of the invention;

FIG. 25 is a flow diagram illustrating yet another example method forassociation management of a wireless node network in accordance with anembodiment of the invention;

FIG. 26 is a flow diagram illustrating an exemplary method for contextmanagement of a wireless node network in accordance with an embodimentof the invention;

FIG. 27 is a flow diagram illustrating an exemplary method for locatinga node in a wireless node network based upon observed signal patternsand characteristic indications over a period of time in accordance withan embodiment of the invention;

FIG. 28 is a flow diagram illustrating an exemplary method for locationdetermination by varying a power characteristic of nodes in a wirelessnode network in accordance with an embodiment of the invention;

FIG. 29 is a flow diagram illustrating an exemplary method for locationdetermination using one or more associations of nodes in a wireless nodenetwork in accordance with an embodiment of the invention;

FIG. 30 is a flow diagram illustrating another exemplary method forlocation determination using one or more associations of nodes in awireless node network in accordance with an embodiment of the invention;

FIG. 31 is a flow diagram illustrating yet another exemplary method forlocation determination using one or more associations of nodes in awireless node network in accordance with an embodiment of the invention;

FIG. 32 is a flow diagram illustrating an exemplary method for locationdetermination of a first node in a wireless node network based oncontext data in accordance with an embodiment of the invention;

FIG. 33 is a flow diagram illustrating an exemplary method fordetermining a location using chaining triangulation for one of aplurality of nodes in a wireless node network having a server inaccordance with an embodiment of the invention;

FIG. 34 is a diagram illustrating an exemplary logistics vehicle inaccordance with an embodiment of the invention;

FIGS. 35A-35C are diagrams illustrating an exemplary mobile node-enabledlogistics receptacle having a lockable opening in exemplary stageschanging from a locked state to an open or unlocked state in order toselectively release an item maintained in a storage area of thereceptacle in accordance with an embodiment of the invention;

FIG. 36 is a flow diagram illustrating an exemplary method for enhanceddelivery management of an item using a mobile node-enabled logisticsreceptacle in accordance with an embodiment of the invention;

FIGS. 37A-37C are diagrams illustrating an exemplary mobile couriermaster node moving between locations with items for pickup or deliveryin accordance with various embodiments of the invention;

FIG. 38 is a flow diagram illustrating an exemplary method forgenerating a corrective delivery notification related to an item by amobile master node involved with delivery of the item in accordance withan embodiment of the invention;

FIG. 39 is a flow diagram illustrating an exemplary method fortransmitting a corrective delivery notification related to an item by amaster node associated with a location in accordance with an embodimentof the invention;

FIG. 40 is a flow diagram illustrating an exemplary method forgenerating a corrective pickup notification related to an item by amobile master node in accordance with an embodiment of the invention;

FIG. 41 is a flow diagram illustrating an exemplary method fortransmitting a corrective pickup notification related to an item by amaster node associated with a location in accordance with an embodimentof the invention;

FIG. 42 is a flow diagram illustrating an alternative exemplary methodfor transmitting a corrective pickup notification related to an item bya master node associated with a location in accordance with anembodiment of the invention;

FIGS. 43A-43B are diagrams illustrating an exemplary master nodeassociated with a fixed location that generates a pickup notificationrelated to an inventory item in accordance with an embodiment of theinvention; and

FIG. 44 is a flow diagram illustrating an exemplary method forgenerating a pickup notification related to an inventory item using anexemplary master node associated with a fixed location in accordancewith an embodiment of the invention.

DESCRIPTION OF THE EMBODIMENTS

Reference will now be made in detail to exemplary embodiments. Whereverpossible, the same reference numbers are used in the drawings and thedescription to refer to the same or like parts.

In general, the following describes various embodiments of acontextually aware hierarchical wireless node network that may bemanaged, operated, and applied by principles as set forth herein. Ingeneral, embodiments of the wireless node network may include one ormore lower level devices or nodes (e.g., an ID node) that rely onshorter-range communication with a higher level device or node (e.g., amaster node), which is operative to communicate with a server over adifferent communication path while the lower level node is unable tocommunicate directly with the server. Those skilled in the art willappreciate that such a hierarchy of different functional communicatingnetwork components (generally referred to as network devices) may becharacterized as a network of nodes. Those skilled in the art willappreciate that in some embodiments, the wireless node network mayinclude the server as well as different wireless nodes despite the factthat the server may not be a dedicated wireless component. In otherembodiments, the network may include similar types of wireless nodes ordifferent types of wireless nodes.

Further, those skilled in the art will appreciate that each embodimentdescribed herein effects improvements to particular technologies, suchas enhanced delivery management that involves selective release of anitem for delivery and generating and/or transmitting corrective deliverynotifications using an adaptive, context-aware wireless node network ofnode elements. Each embodiment describes a specific technologicalapplication of one or more nodes that operate in such a wireless nodenetwork where the specific technological application improves orotherwise enhances such technical fields as explained and supported bythe disclosure that follows.

Those skilled in the art will understand through the following detaileddescription that the nodes may be associated with items (e.g., anobject, a package, a person, a piece of equipment) and may be used toidentify, locate, track, and manage the items while being dynamicallyprogrammed during operation of the network and while the items movealong an anticipated path (e.g., a transit path from an origin point toa destination point). The following further describes variousembodiments of a wireless node network, exemplary ways to managecomponents of a wireless node network, exemplary ways to betterdetermine the location of components of a wireless node network, andapplications of a wireless node network to enhance logistics operationsthat rely upon a wireless node network.

Wireless Node Networks

FIG. 1 illustrates a basic diagram of an exemplary wireless node networkin accordance with an embodiment of the invention. The exemplary networkshown in FIG. 1 comprises a server 100 connected to a network 105, whichis also operatively connected to different network components, such as amaster node 110 a and indirectly to an ID node 120 a through master node110 a. Master node 110 a is typically connected to an ID node 120 a viashort-range wireless communications (e.g., Bluetooth® formattedcommunications). Master node 110 a is typically connected to server 100through network 105 via longer-range wireless communication (e.g.,cellular) and/or medium range wireless communication (e.g., wirelesslocal area data networks or Wi-Fi). ID node 120 a is typically a lowcost device that may be easily placed into a package, be integrated aspart of packaging, or otherwise associated with an item to be trackedand located, such as package 130, a person, or object (e.g., vehicle,etc.). Generally, an ID node is capable of communicating directly with amaster node but incapable of communicating directly with the server,while a master node is capable of communicating directly with the serverand separately and directly communicating with other nodes (such as anID node or another master node). The ability to deploy a hierarchy ofnodes within an exemplary wireless node network to distribute tasks andfunctions at the different levels in an efficient and economical mannerhelps to facilitate a wide variety of adaptive locating, tracking,managing, and reporting applications using such a network of nodes asdiscussed in more detail below.

In general, the lower cost, lower complexity ID node 120 a is managed bythe higher complexity master node 110 a and server 100 as part ofkeeping track of the location of ID node 120 a (and the associateditem), thereby providing intelligent, robust, and broad visibility aboutthe location and status of ID node 120 a. In a typical embodiment, IDnode 120 a is first associated with an item (e.g., package 130, aperson, or object). As ID node 120 a moves with the item, the ID node120 a becomes associated with the master node 110 a, and the server 100is updated with such information. Further movement of the ID node 120 aand item may cause the ID node 120 a to disassociate with master node110 a and be handed off to become associated another master node (notshown), after which the server 100 is again updated. As such, the server100 generally operates to coordinate and manage information related tothe ID node 120 a as the item physically moves from one location toanother. Further details of the architecture and functionality of anembodiment of an exemplary ID node and master node as described below inmore detail with respect to FIGS. 3 and 4, while exemplary server 100 isdescribed below in more detail with respect to FIG. 5.

While server 100 is shown connecting through network 105, those skilledin the art will appreciate that server 100 may have a more direct ordedicated connections to other components illustrated in FIG. 1, such asmaster node 110 a, depending upon implementation details and desiredcommunication paths. Furthermore, those skilled in the art willappreciate that an exemplary server may contain a collection ofinformation in a database (not shown in FIG. 1), while multipledatabases maintained on multiple server platforms or network storageservers may be used in other embodiments to maintain such a collectionof information. Furthermore, those skilled in the art will appreciatethat a database may be implemented with cloud technology thatessentially provides networked storage of collections of informationthat may be directly accessible to devices, such as master node 110 a.

Network 105 may be a general data communication network involving avariety of communication networks or paths. Those skilled in the artwill appreciate that such exemplary networks or paths may be implementedwith hard wired structures (e.g., LAN, WAN, telecommunication lines,telecommunication support structures and telecommunication processingequipment, etc.), wireless structures (e.g., antennas, receivers,modems, routers, repeaters, etc.) and/or a combination of both dependingupon the desired implementation of a network that interconnects server100 and other components shown in FIG. 1 in an embodiment of the presentinvention.

Master node 110 a and ID node 120 a are types of nodes. A node isgenerally an apparatus or device used to perform one or more tasks aspart of a network of components. An embodiment of a node may have aunique identifier, such as a Media Access Control (MAC) address or anaddress assigned to a hardware radio like an Internet Protocol 6 (IPv6)identifier. In some embodiments, the node's unique identifier may becorrelated to a shipment identifier (e.g., a shipment tracking number inone example), or may itself be a shipment's tracking reference.

An ID node, such as ID node 120 a, is generally a low cost activewireless device. In one embodiment, an exemplary ID node is atransceiver-based processing or logic unit having a short-range radiowith variable RF characteristics (e.g., programmable RF output powerrange, programmable receiver sensitivity), memory accessible by theprocessing unit, a timer operatively coupled to the processing unit, anda power source (e.g., a battery) that provides power for the circuitryof the ID node. For example, the physical implementation of an exemplaryID node may be small, and, thus, amenable to integration into a package,label, container, or other type of object. In some implementations of anID node, the node is rechargeable while other implementations do notpermit recharging the power source for the ID node. In otherimplementations, the ID node is environmentally self-contained or sealedso as to enable robust and reliable operations in a variety ofenvironmentally harsh conditions.

A master node, such as master node 110 a, generally serves as anintelligent bridge between the ID node 120 a and the server 100.Accordingly, a master node is generally more sophisticated than an IDnode. In one example embodiment, an exemplary master node is a devicehaving a processing or logic unit, a short-range radio (with may havevariable RF characteristics) used for communicating with other nodes (IDnodes and other master nodes), a medium and/or long-range radio forcommunication with the server 100, memory accessible by the processingunit, a timer operatively coupled to the processing unit, and a powersource (e.g., a battery or a wired power supply connection) thatprovides power for the circuitry of the master node. The exemplarymaster node, such as master node 110 a, may be positioned in a knownfixed location or, alternatively, be a mobile unit having dedicatedlocation positioning circuitry (e.g., GPS circuitry) to allow the masternode to determine its location by itself.

While the embodiment illustrated in FIG. 1 shows only a single masternode and a single ID node, those skilled in the art will appreciate thata wireless network consistent with an embodiment of the invention mayinclude a wide array of similar or different master nodes that eachcommunicate with the server 100 and/or other master nodes, and a widevariety of similar or different ID nodes. Thus, the exemplary networkshown in FIG. 1 is a basic embodiment, while the exemplary network shownin FIG. 2 is a more detailed exemplary wireless node network inaccordance with another embodiment of the invention.

Referring now to FIG. 2, another exemplary wireless node network isshown including server 100 and network 105. Here, master nodes 110 a,110 b, 110 c are deployed and connected to network 105 (and by virtue ofthose respective connections, to server 100) as well as to each other.ID nodes 120 a, 120 b, 120 e are shown as connectable or operative tocommunicate via different paths to various master nodes. However, IDnodes 120 c and 120 d are shown in FIG. 2 connected to ID node 120 b butnot to any of the master nodes. This may be the case if, for example, IDnodes 120 b, 120 c, 120 d are associated with different items (e.g.,packages) within a larger container 210 (or grouped together on apallet). In such an example, only ID node 120 b may remain within thewireless communication range of any master node. This may, for example,be because of the positions of the different ID nodes within thecontainer relative to the closest master node, adverse RF shieldingcaused by the container, adverse RF shielding caused by packaging of theitem, or adverse RF shielding caused by other proximate material thatinterferes with radio transmissions (e.g., several packages of metalitems between the ID node and any master node outside the container).Thus, in the illustrated configuration of the exemplary network shown inFIG. 2, ID nodes 120 c and 120 d may be out of range from the masternodes, yet still have an operative communication path to a master nodethrough ID node 120 b.

Indeed, in one example, prior to placement within container 210, ID node120 b may actually be a master node but the changed RF environment whenplacing it in container 210 may interfere with the master node's abilityto locate itself via location signals (e.g., GPS signals) and cause themaster node to temporarily operate as an ID node while still providingcommunications and data sharing with other ID nodes in container 210.

User access devices 200, 205 are also illustrated in FIG. 2 as beingable to connect to network 105, master nodes, and ID nodes. Generally,user access devices 200 and 205 allow a user to interact with one ormore components of the exemplary wireless node network. In variousembodiments, user access devices 200, 205, may be implemented using adesktop computer, a laptop computer, a tablet (such as an Apple iPad®touchscreen tablet), a personal area network device (such as aBluetooth® device), a smartphone (such as an Apple iPhone®), a smartwearable device (such as a Samsung Galaxy Gear™ smartwatch device, or aGoogle Glass™ wearable smart optics) or other such devices capable ofcommunicating over network 105 with server 100, over a wired or wirelesscommunication path to master node and ID nodes. Thus, an exemplary useraccess device may be a mobile type of device intended to be easily moved(such as a tablet or smartphone), and may be a non-mobile type of deviceintended to be operated from a fixed location (such as a desktopcomputer).

As shown in FIG. 2, user access devices 200, 205 are coupled and incommunication with network 105, but each of them may also be incommunication with each other or other network components in a moredirect manner (e.g., via near field communication (NFC), over aBluetooth® wireless connection, over a Wi-Fi network, dedicated wiredconnection, or other communication path).

In one example, a user access device, such as device 200 or 205, mayfacilitate associating an ID node (such as ID node 120 a) with thetracking number of a package at the start of a shipment process,coordinating with the server 100 to check on the status and/or locationof the package and associated ID node during transit, and possiblyretrieving data from a master node or ID node related to the shippedpackage. Thus, those skilled in the art will appreciate that a useraccess device, such as devices 200, 205, are essentially interactivecommunication platforms by which a user may initiate shipment of anitem, track an item, determine the status and location of an item, andretrieve information about an item.

An exemplary user access device, such as device 200 or 205, may includesufficient hardware and code (e.g., an app or other program code sectionor sections) to operate as a master node or an ID node in variousembodiments as discussed in more detail below. For example, device 200may be implemented as a mobile smartphone and functionally may operateas an exemplary ID node that broadcasts advertising packet messages toother ID nodes or master nodes for association and sharing data withsuch nodes. In another example, device 200 is implemented as a mobilesmartphone and may operate as an exemplary master node that communicatesand associates with ID nodes and other master nodes, as describedherein, and communicates with the server 100. Thus, those skilled in theart will appreciate an exemplary ID node in FIG. 3 and an exemplarymaster node in FIG. 4, and their respective parts, code and programmodules, may be implemented with an appropriately programmed user accessdevice, such as device 200 or 205. Thus, the following description of anexemplary ID node in FIG. 3 and an exemplary master node in FIG. 4 willbe applicable to a user access device operating as an ID node or amaster node, respectively.

ID Node

FIG. 3 is a more detailed diagram of an exemplary ID node device inaccordance with an embodiment of the invention. As previously described,one embodiment of an ID node includes a transceiver-based processing orlogic unit having a short-range radio with variable RF characteristics(e.g., programmable RF output power range, programmable receiversensitivity), memory accessible by the processing unit, a timeroperatively coupled to the processing unit, and a power source (e.g., abattery) that provides power for the circuitry of the ID node. Referringnow to the more detailed embodiment of FIG. 3, exemplary ID node 120 ais shown to comprise a processing or logic unit 300 coupled to avariable power short-range communication interface 375, memory storage315, volatile memory 320, timer 370, and battery 355. Those skilled inthe art will appreciate that processing unit 300 is logic, such as a lowpower consumption microcontroller, that generally performs computationson data and executes operational and application program code and otherprogram modules or sections thereof within the ID node 120 a. As such,exemplary processing unit 300 operates as a transceiver-based processingcore of ID node 120 a.

Those skilled in the art will also appreciate that exemplary ID node 120a is a hardware-based component that may be implemented with a singleprocessor or logic unit, such as unit 300. In one embodiment, processingunit 300 may be implemented with an Intel® 8051 CPU Core and associatedperipheral circuitry as dictated by the needs of the particularapplication. Less complex microcontrollers or discrete circuitry may beused to implement processing unit 300 as well as more complex andsophisticated microprocessors. Additionally, exemplary processing unit300 may be integrated into a single chip transceiver used as a core ofID node 120 a.

The variable power short-range communication interface 375 of ID node120 a is generally a programmable radio and an omni-directional antennacoupled to the processing unit 300. In other embodiments, interface 375may use an antenna with a different antenna profile when directionalitymay be desired. Examples of variable power short-range communicationinterface 375 may include other interfacing hardware (not shown) foroperatively coupling the device to a specific short-range communicationpath (e.g., a Bluetooth® Low Energy (BLE) connection path communicatingat 2.4 GHz).

In one embodiment, various RF characteristics of the radio'stransceiver, such as the RF output power and/or the RF receiversensitivity may be dynamically and programmatically varied under controlof processing unit 300. In other embodiments, further RF characteristicsof the radio's transceiver may be programmatically varied, such asfrequency, duty cycle, timing, modulation schemes, spread spectrumfrequency hopping aspects, etc., as needed to flexibly adjust the RFoutput signal depending upon a desired implementation and anticipateduse of ID node 120 a. As will be explained in more detail below, someembodiments may use Broadcast Profile having parameters that may beprogrammatically altered or adjusted. In other words, embodiments of IDnode 120 a (or any other ID node) may have programmatically adjustableRF characteristics (such as an adjustable RF output signal power, anadjustable RF receiver sensitivity, the ability to switch to a differentfrequency or frequency band, etc.).

The battery 355 for ID node 120 a is a type of power source thatgenerally powers the circuitry implementing ID node 120 a. In oneembodiment, battery 355 may be a rechargeable power source. In otherembodiments, battery 355 may be a non-rechargeable power source intendedto be disposed of after use. In some embodiments of an ID node, thepower source may involve alternative energy generation, such as a solarcell.

The timer 370 for ID node 120 a generally provides one or more timingcircuits used in, for example, time delay, pulse generation, andoscillator applications. In an embodiment where ID node 120 a conservespower by entering a sleep or dormant state for a predetermined timeperiod as part of overall power conservation techniques, timer 370assists processing unit 300 in managing timing operations. Additionally,an embodiment may allow an ID node to share data to synchronizedifferent nodes with respect to timer 370 and a common timing referencebetween nodes and the server.

An embodiment may implement ID node 120 a to optionally include a basicuser interface (UI) 305 indicating status and allowing basic interactionlike start/stop. In one embodiment, the UI 305 may be implemented withstatus lights, such as multi-mode LEDs. Different colors of the lightsmay indicate a different status or mode for the ID node 120 a (e.g., anadvertising mode (broadcasting), a scanning mode (listening), a currentpower status, a battery level status, an association status, an error,as sensed condition (e.g., exceeding a temperature threshold, exceedinga moisture threshold, and the like)). Other embodiments of an ID nodemay implement U! 305 in a more sophisticated manner with a graphicsdisplay or the like where such status or mode information may bedisplayed as well as one or more prompts.

In a further embodiment, an exemplary status light used as part of theUI 305 of an ID node may also indicate a shipment state. In more detail,an exemplary shipment state may include a status of the shipped item ora status of the item's current shipment journey from an origin to adestination.

An embodiment may also implement ID node 120 a to optionally include oneor more sensors 360. In some embodiments, an ID node implemented withone or more sensors 360 may be referred to as a Sensor node. Examples ofsensor 360 may include one or more environmental sensors (e.g.,pressure, movement, light, temperature, humidity, magnetic field,altitude, attitude, orientation, acceleration, etc.) and dedicatedlocation sensors (e.g., GPS sensor, IR sensor, proximity sensor, etc.).Those skilled in the art will understand that additional types ofsensors that measure other characteristics are contemplated for use assensor 360. Additionally, those skilled in the art will understand thata Sensor node may include additional program features to manage thecollection, storage, sharing, and publication of the captured sensordata.

An embodiment may further implement ID node 120 a to optionally includeone or more magnetic switches 365. A magnetic switch 365, such as a reedswitch, generally operates to close or open an electrical path orconnection in response to an applied magnetic field. In other words,magnetic switch 365 is actuated by the presence of a magnetic field orthe removal of a magnetic field. Various applications, as discussed inembodiments described in more detail below, may involve the operation ofID node 120 a having magnetic switch 365.

Consistent with the embodiment shown in FIG. 3, exemplary ID node 120 amay be implemented based upon a Texas Instruments CC2540 Bluetooth® LowEnergy (BLE) System-on-Chip, which includes various peripherals (e.g.,timer circuitry, USB, USART, general-purpose I/O pins, IR interfacecircuitry, DMA circuitry) to operate as an ID node and, if necessary, tointerface with different possible sensors and other circuitry (e.g.,additional logic chips, relays, magnetic switches) that make up the IDnode.

In additional embodiments, one skilled in the art will appreciate thatsimilar functionality in an ID node may be implemented in other types ofhardware. For example, ID node 110 a may be implemented with speciallyoptimized hardware (e.g., a particular application specific integratedcircuit (ASIC) having the same operational control and functionality asnode control and management code, as described below, discrete logic, ora combination of hardware and firmware depending upon requirements ofthe ID node, such as power, processing speed, level of adjustability forthe RF characteristics, number of memory storage units coupled to theprocessor(s), cost, space, etc.

As noted above, ID node 120 a includes memory accessible by theprocessing unit 300. Memory storage 315 and volatile memory 320 are eachoperatively coupled to processing unit 300. Both memory componentsprovide programming and data elements used by processing unit 300. Inthe embodiment shown in FIG. 3, memory storage 315 maintains a varietyof program code (e.g., node control and management code 325) and otherdata elements (e.g., profile data 330, security data 335, associationdata 340, shared data 345, sensor data 350, and the like). Memorystorage 315 is a tangible, non-transient computer readable medium onwhich information (e.g., executable code/modules, node data, sensormeasurements, etc.) may be kept in a non-volatile and non-transitorymanner. Examples of such memory storage 315 may include a hard diskdrive, ROM, flash memory, or other media structure that allows longterm, non-volatile storage of information. In contrast, volatile memory320 is typically a random access memory (RAM) structure used byprocessing unit 300 during operation of the ID node 120 a. Upon power upof ID node 120 a, volatile memory 320 may be populated with anoperational program (such as node control and management code 325) orspecific program modules that help facilitate particular operations ofID node 120 a. And during operation of ID node 120 a, volatile memory320 may also include certain data (e.g., profile data 330, security data335, association data 340, shared data 345, sensor data 350, and thelike) generated as the ID node 120 a executes instructions as programmedor loaded from memory storage 315. However, those skilled in the artwill appreciate that not all data elements illustrated in FIG. 3 mustappear in memory storage 315 and volatile memory 320 at the same time.

Node Control & Management Code

Generally, an embodiment of node control and management code 325 is acollection of software features implemented as programmatic functions orprogram modules that generally control the behavior of a node, such asID node 120 a. In an embodiment, the functionality of code 325 may begenerally similar as implemented in different types of nodes, such as amaster node, an ID node, and a sensor node. However, those skilled inthe art will appreciate that while some principles of operation aresimilar between such nodes, other embodiments may implement thefunctionality with some degree of specialization or in a differentmanner depending on the desired application and use of the node.

In a general embodiment, exemplary node control and management code 325may generally comprise several programmatic functions or program modulesincluding (1) a node advertise and query (scan) logic manager (alsoreferred to herein as a node communications manager), which manages howand when a node communicates; (2) an information control and exchangemanager, which manages whether and how information may be exchangedbetween nodes; (3) a node power manager, which manages power consumptionand aspects of RF output signal power and/or receiver sensitivity forvariable short-range communications; and (4) an association managerfocusing on how the node associates with other nodes. What follows isdescription of various embodiments of these basic program modules usedby nodes.

Node Communications Manager—Advertising & Scanning

In an exemplary embodiment, the node advertise and query (scan) logicmanager governs how and when a node should advertise (transmit) itsaddress or query (scan) for the address of neighboring nodes.Advertising is generally done with a message, which may have differentinformation in various parts (e.g., headers, fields, flags, etc.). Themessage may be a single or multiple packets.

In the exemplary embodiment, the “advertise” mode (as opposed to “query”or “scan” mode) is a default mode for an ID Node and has the nodebroadcasting or transmitting a message with its address and relatedmetadata regarding the node. For example, in one embodiment, exemplarymetadata may include information such as the RF output power level, areference number, a status flag, a battery level, and a manufacturername for the node.

FIG. 6 is a diagram illustrating the structure or format of an exemplaryadvertisement data packet in accordance with a general embodiment of theinvention. Referring now to FIG. 6, the structure of an exemplaryadvertisement data packet 600 broadcast as a signal or message from anID node, such as ID node 120 a, is shown. Packet 600 appears with anincreasing level of detail showing exemplary metadata and a format thatseparately maintains distinct types of metadata in different parts ofthe packet. Different embodiments may include different types ofmetadata depending on the deployed application of the ID node.

FIG. 7 is a diagram illustrating sample content for an exemplaryadvertisement data packet in accordance with an embodiment of theinvention. Referring now to FIG. 7, an exemplary advertisement datapacket 700 is illustrated with exemplary metadata including showingsample information such as the RF Output Power level (e.g., “TX PowerLevel”), a reference number (e.g., “‘FDX ID’ (ASCII Short Name)”, astatus flag (e.g., “Status Flag Value (indicates ‘Ack Requested’)”), abattery level (e.g., “Battery Level Value (Indicates 73% charge)”, and amanufacturer name for the node (e.g., “Company Identifier (currentlyundefined for FedEx)”). In one embodiment, those skilled in the art willappreciate that the reference number may be omitted or obfuscated forsecurity purposes.

In one embodiment, an exemplary advertising data packet may include theRF Output power level, as noted above in FIG. 7, to enable one way tohelp identify the type of node doing the broadcasting and the locationof the broadcasting node. However, if the broadcast RF output powerlevel is fixed and known by the node type, only the node type need beidentifiable from an exemplary advertising data packet, such as packet700.

Regarding how a node communicates, an exemplary node may be in one ofseveral different communication modes. A node in an advertising (ortransmit or broadcast) mode is visible to any other node set in a query(or scan or listen) mode. In an embodiment, the frequency and length ofadvertising may be application and power dependent. For example, innormal operations, an exemplary node will generally advertise in aperiodic manner and expect to make an active connection to another nodeat certain intervals, which may be dictated by conditions set by server100. In an embodiment, such conditions may be set individually for anode by the server or a higher level node in the network.

If an exemplary node has not received acknowledgement for an advertisingpacket within a particular period, it may enter one or more alertstages. For example, if an exemplary node has not receivedacknowledgement from another node for an advertising packet broadcast bythe exemplary node within a particular time period (also generallyreferred to as an Alert Interval), the exemplary node will enter anAlert Stage 1 status. This prompts the exemplary node to issue afollow-up advertising packet having one or more parts of it altered toindicate the Alert Stage 1 status. In more detail, this exemplaryfollow-up advertising packet may have a different advertising alertheader instructing nearby nodes to send a SCAN_REQ message uponreceiving an advertisement packet.

If an exemplary node has not received acknowledgement from a master nodefor an advertising packet broadcast by the exemplary node within anothertime period (e.g., a request from the master node to actively connectand a success connection made), it will enter another alert stage, suchas an Alert Stage 2 status. This prompts the exemplary node to issue afollow-up advertising packet having one or more parts of it altered toindicate the Alert Stage 2 status. In more detail, this exemplaryfollow-up advertising packet may have a different advertising alertheader instructing nearby master nodes to send a SCAN_REQ message uponreceiving an advertisement packet.

If an exemplary node has data to upload to the backend, it may alsoenter another type of alert stage. In one embodiment, for example, if anexemplary node has sensor data collected by the exemplary node (orreceived from one or more other nodes that have communicated with theexemplary node), and the data needs to be uploaded to server 100, theexemplary node may enter an update alert stage, such as an Alert Stage3. This prompts the exemplary node to issue a follow-up advertisingpacket having one or more parts of it altered to indicate the AlertStage 3 status. In more detail, this exemplary follow-up advertisingpacket may have a different advertising alert header instructing nearbymaster nodes to make a connection with the exemplary node so that thedata (e.g., sensor data 350) may be transmitted from the exemplary node(e.g., ID node 120 a) to a nearby master node (e.g., master node 110 a).The transmitted data may then be stored by the nearby master node assensor data 450 in either or both of the master node's volatile memory420 and memory storage 415. Subsequent to that storage operation, thenearby master node will transfer the data (e.g., sensor data 450) toserver 100.

As illustrated in FIG. 7 and explained in the above description of alertlevel stages, a status flag in a header of an exemplary advertising datapacket is a field used in the association logic in one or moreembodiments. For example, in one embodiment, the existence of a statusflag in the advertising data packet allows a first node to communicateits status to a second node, and for the second node to report thatstatus to the backend server, such as server 100, without an activedirect connection from the first node to the server. In other words, thestatus flag helps facilitate passive interactions between nodes (such aspassive associations).

In a more detailed embodiment, several exemplary status types areestablished with respect to communications with other nodes. Forexample, the exemplary status types may comprise the following:

-   -   Alert Level 0—no issue, operating normal;    -   Alert Level 1—The advertising node is requesting that any        available node acknowledge the receipt of its advertisement        packet;    -   Alert Level 2—The advertising node is requesting that any        available master node acknowledge the receipt of its        advertisement packet;    -   Alert Level 3—Data for Upload—node has captured data available        for upload through a master node; and    -   Synchronize—The advertising node requests to connect with a        device or sensor that can synchronize data (such as timer or        location information).

By broadcasting the status via, for example, a portion of a header in anadvertising data packet, one or more nodes within range of thebroadcasting node can determine the node's status and initiate activeconnections if requested in the status message.

A request for more information from the advertising node may, in someembodiments, come in the form of a SCAN_REQ message. In general, anexemplary SCAN_REQ is a message sent from a scanning (listening) masternode to an advertising node requesting additional information from theadvertising node. In this example, the alert status bit may indicate tothe scanning master node, for example, at an application layer, whetherthe advertising node is in a mode that will or will not accept aSCAN_REQ. In one embodiment, the non-connectable and discoverable modesof node advertising are in compliance with Bluetooth® Low Energy (BLE)standards.

In another embodiment, a node may have further different modes ofoperation while scanning or listening for other nodes. For example, anode's query or scanning mode may be active or passive. When a node isscanning while passive, the node will receive advertising data packets,but will not acknowledge and send SCAN_REQ. However, when a node isscanning while active, the node will receive advertising data packets,and will acknowledge receipt by sending a SCAN_REQ. A more detailedembodiment may provide the passive and active modes of scanning orinquiry in compliance with Bluetooth® Low Energy (BLE) standards.

In an embodiment, an exemplary node is scanning as it listens for otherwireless nodes broadcasting on the short-range radio. An exemplaryscanning node may capture, for example, a MAC address of the advertisingnode, a signal strength of the RF output signal transmitted from theadvertising node, and any other metadata published by the advertisingnode (e.g., other information in the advertising data packet). Thoseskilled in the art will appreciate that the scope of “listening” when anode is scanning may vary. For example, the query may be limited. Inother words, the scope of what a node is particularly interested in andfor which it is listening may be focused or otherwise limited. In such acase, for example, the information collected may be limited toparticular information from a targeted population of short-rangewireless nodes advertising; but the information collection may beconsidered “open” where information from any advertising device iscollected.

When nodes are advertising or scanning, an embodiment may make furtheruse of status flags and additional modes when advertising or scanning aspart of how nodes communicate and may be managed. In one example, when ascanning (listening) node receives an advertising data packet with thestatus flag indicating an Alert Level 1 or 2 status, and the scanningnode is in “Passive” scanning mode, the node will switch to “Active”scanning mode for some interval. However, when the scanning node in thissituation is already in an “Active” scanning mode, the node will sendthe SCAN_REQ message and receive a SCAN_RSP from the advertising node(e.g., a message providing the additional information requested from theadvertising node). The scanning node will then switch back to a“Passive” scanning mode.

In another example, when an advertising (broadcasting) node receives aSCAN_REQ from a scanning node, the advertising node will consider thatits advertising data packet has been acknowledged. Further, theadvertising node will reset its “Alert” status flag back to an AlertLevel 0 status. This allows the advertising node to effectively receivean acknowledgement to its advertisement without ever making a connectionto the scanning node, which advantageously and significantly saves onpower consumption.

In yet another example, when a scanning node receives an advertisingdata packet with an Alert Level 3 status flag set, the scanning nodewill attempt to make a connection with the advertising device. Once theconnection is made, the advertising device will attempt to upload itsdata to the connected device

Thus, an embodiment of the node advertise and query (scan) logic managerof code 325 may rely upon one or more status flags, advertising modes,scanning modes, as nodes communicate with each other in variousadvantageous manners.

Node Information Control & Exchange Manager

In an exemplary embodiment, the information control and exchange managerpart of node control and management code 325 determines whether and howinformation may be exchanged between nodes. In the exemplary embodiment,the information control and exchange manager establishes different nodeoperational states where information may be changed according to adesired paradigm for the state. In more detail, an embodiment ofinformation control and exchange manager may establish different levelsof information exchange between nodes with a “non-connectableadvertising” state or mode of operation, a “discoverable advertising”state or mode, and a “general advertising” state or mode operation. Whena node is in the “non-connectable advertising” mode, the nodeinformation exchange is limited. For example, the advertising node maybroadcast information that is captured by one or more querying(scanning) nodes, but no two-way exchange of information happens.

When a node is in the “discoverable advertising” mode and a scanningnode is in “Active” mode, the node information exchange in enabled bothways. For example, the advertising node sends the advertising packet,and in response the scanning node sends the SCAN_REQ packet. After theadvertising node receives the SCAN_REQ requesting additionalinformation, the advertising node sends the SCAN_RSP with the requestedinformation. Thus, in the “discoverable advertising” mode there is atwo-way exchange of information, but no active connection is madebetween the two nodes exchanging information.

Finally, for advanced two-way information exchange, an active connectionmay be used between nodes and information may be exchanged both ways toand from different nodes. In a more detailed embodiment, at this levelof two-way information exchange, nodes are first identified and thenauthenticated as part of establishing the active connection. Onceauthenticated and thereafter actively connected to each other, the nodesmay securely share information back and forth. In one example, a sensornode uploading previously captured environmental information to a masternode may be in this mode or state. In another example, an ID nodeuploading the stored results of a node scanning operation to a masternode may be in this mode or state. In yet another example, a master nodesharing a timer and/or location information with corresponding nodes maybe in this mode or state.

Node Power Manager

In an exemplary embodiment, the node power manager part of node controland management code 325 focuses on managing power consumption and theadvantageous use of power (e.g., an adjustable level of RF output signalpower) in a node. In general, nodes are either powered by a battery(such as battery 355 in an ID node), or by an interface (such asbattery/power interface 470 in a master node) to an external powersource. Examples of an external power source may include, in someembodiments, power supplied from an outlet or power connection within afacility, or power generated onboard a conveyance (e.g., automobile,truck, train, aircraft, ship, etc.). Those skilled in the art willappreciate that an interface to an external power source will begenerally referred to as a “wired” power connection, and that node powermanager may be informed whether a node is wired or powered off abattery, such as battery 355. Further embodiments may implement aninterface to an external power source with wireless power transmission,such as via inductive coils.

In one embodiment, a node may manage power used when performing tasks.For example, a node may manage power when determining which node shouldperform a particular task. In more detail, the collective powerconsumption of a group of devices may be managed by electing to employwired nodes, when feasible or desired, to accomplish a particular task,and saving the battery-powered nodes for other less energy burdensome ortaxing tasks. In another embodiment, historic data may inform the systemof the power needed to accomplish a particular task, and the system maymake a determination of which node should accomplish the particular taskbased upon such historic data. In other embodiments, profile data mayalso be used to inform the system of the power needed to accomplish aparticular task (e.g., a sensor profile that describes powerrequirements for operation of a sensor node that gathers sensor dataover a certain period of time and under certain conditions). The systemmay also make a determination of which node should accomplish theparticular task based upon such profile data.

In another example, the exemplary node power manager may manage powerwhen determining how to best to use and adjust power to more accuratelyaccomplish a particular task. In one embodiment, an RF signal outputfrom a node (such as a short-range RF output signal from an ID node) mayperiodically move through a range of output power or simply switchbetween two or more settings that differ in a detectable manner. Asdisclosed in more detail below, the variability and dynamic adjustmentof RF output signal power may allow other nodes (such as one or moremaster nodes) to see each node at the upper range of the RF outputsignal power, and only see nodes physically close to the advertisingnode at the lower range of signal power.

In another example, the exemplary node power manager may cause a changeto a characteristic of its RF output signal power when the node has beenassociated to a physical place or another node by virtue of context data(such as context data 560 and association logic that utilizes that typeof information). In one embodiment, the node may be instructed to changehow often the node communicates and/or a characteristic of its RF outputpower to preserve power.

In yet another example, all advertising nodes may have their respectivenode power managers periodically cause each respective node to broadcastat a maximum RF output signal power level to ensure they still arewithin range of a scanning ID Node or Master Node. Doing so may increasethe chance of being in communication range and allows the individualnodes to be properly located and managed within the network. Thebroadcast duration may be set or dynamically changed to allow pairing tooccur if needed.

Rather than adjust the RF output signal power level, the exemplary nodepower manager may, in some embodiments, adjust the RF receiversensitivity of a node. This allows for an adjustable range of reception(as opposed to merely an adjustable range of broadcast), which maysimilarly be used to manage power and enhance location determinations asdiscussed herein.

In yet another embodiment, a combination approach may be used in whichthe node power manager may concurrently and independently adjust morethan one RF characteristic of a node. For example, en exemplary nodepower manager may adjust an RF output signal power level and also adjustthe RF receiver sensitivity of a node as the node is located andassociated with other nodes. Those skilled in the art will realize thatthis may be especially useful in an area with an unusually denseconcentration of nodes, and a combination of changing RF output signalpower levels

An embodiment of the exemplary node manager may refer to a power profile(e.g., an exemplary type of profile data 330, 430) when adjusting anode's power characteristics (e.g., consumption of power, use of power,output signal frequency, duty cycle of the output put signal, timing,power levels, etc.).

Node Association Manager

In an exemplary embodiment, the node association manager part of nodecontrol and management code 325 focuses on how the nodes associate withother nodes in conjunction and consistent with the server-sideassociation manager in code 525, as discussed in more detail below.Thus, exemplary node association manager, when executing in a node,directs how the node associates (e.g., enters an active connection mode)with one or more other nodes with input from the server.

The exemplary node association manager for a node may indicate through aStatus Flag if the node requires an acknowledgement or connection, or ifit has information available for upload to the backend. Thus, while anode may not be associated or actively connected yet to another node, astatus of the node may be inferred from, for example, the statusinformation in the node's broadcast header.

Regarding connections between nodes, there are generally secureconnections and unsecure connections. While an embodiment may allowunsecure connections between one or more sets of nodes, otherembodiments rely upon secure connections or authenticate pairings ofnodes. In one embodiment, for a node to pair with another node, theexemplary node association manager first identifies the nodes to beassociated and transmits an association request to the server. Therequest may include a specific request to pair the nodes and ask for thecorresponding pairing credentials from the server, such as server 100.The server 100 may have staged pairing credentials on particular nodesbased on information indicating the nodes would be within wirelessproximity and future pairing may occur. Visibility to the noderelationship may have been determined through scan-advertising, or3^(rd) party data such as barcode scan information indicating the nodesto be within proximity currently or at a future state.

When connecting or not connecting to exchange information under theexemplary node information exchange modes described above, nodesgenerally operate in a number of states, which make up an exemplaryadvertise cycle for an exemplary ID node. Such an exemplary advertisecycle for a node is further explained below with reference to FIG. 8 andin conjunction and consistent with the server-side association managerin code 525, as discussed in more detail below.

Airborne Mode Program Module

In one embodiment, node control and management code 325 may also includean airborne mode program module (not shown). In another embodiment, theairborne mode program module may be implemented as a part of the nodepower manager program module of code 325. An exemplary airborne modeprogram module generally operates to manage the output power of the IDnode's variable power short-range communication interface 375 when theID node is operating in an aircraft. Operating a wireless device withinan aircraft may, in some circumstances, have an unintentional impact onother electronic systems on the aircraft. In more detail, an embodimentof the airborne mode program module may operate to transition the IDnode from different states or modes depending upon particular operationsand/or operational conditions of the aircraft. For example, an exemplaryairborne mode program module may operate to transition the ID node fromone state or mode (e.g., a normal mode prior to takeoff, a disabled modeduring takeoff, an airborne mode while aloft, a disabled mode duringdescent, and a normal mode after landing) based upon detectedenvironmental conditions (e.g., pressure, altitude) and/or flight detailinformation associated with the aircraft. In this way, an ID node may beallowed to normally operate when onboard an aircraft, be disabled fromoperating at all in some circumstances, and be able to operate in anairplane mode that allows sensing and sensor data capture, but that maylimit transmission of an RF output signal to avoid interference with theaircraft's onboard electronics. Further information related to a methodof managing a wireless device (such as an ID node) in an aircraft isdisclosed in greater detail in U.S. patent application Ser. No.12/761,963 entitled “System and Method for Management of WirelessDevices Aboard an Aircraft,” which is hereby incorporated by reference.

Node Data

As previously noted, volatile memory 320 may also include certain data(e.g., profile data 330, security data 335, association data 340, shareddata 345, sensor data, and the like) generated as the ID node 120 aexecutes instructions as programmed or loaded from memory storage 315.In general, data used on a node, such as an ID node, may be receivedfrom other nodes or generated by the node during operations.

In one embodiment, profile data 330 is a type of data that defines ageneral type of behavior for an ID node, such as a Broadcast Profile(discussed in more detail below). In another embodiment where ID node120 a is a BLE device, profile data 330 may include a Bluetooth®compatible profile related to battery service (exposing the state of abattery within a device), proximity between BLE devices, or messagingbetween BLE devices. Thus, exemplary profile data 330 may exist involatile memory 320 and/or memory storage 315 as a type of data thatdefines parameters of node behavior.

In one embodiment, it may be desired to allow secured pairings of nodes.As will be explained in more detail below, as part of secure pairing ofnodes, a request for pairing credentials is generated and sent to server100. Thus, exemplary security data 335 (e.g., PIN data, securitycertificates, keys, etc.) may exist in volatile memory 320 and/or memorystorage 315 as a type of data associated with providing securedrelationships between nodes, such as the requested security credentials.

Association data, such as association data 340, generally identifies aconnected relationship between nodes. For example, ID node 120 a maybecome associated with the master node 110 a as the ID node 120 a moveswithin range of the master node 110 a and after the server directs thetwo nodes to associate (with authorization). As a result, informationidentifying the relationship between ID node 120 a and master node 110 amay be provided to server 100 and may be provided, as some point, toeach of ID node 120 a and master node 110 a. Thus, exemplary associationdata 340 may exist in volatile memory 320 and/or memory storage 315 as atype of data identifying associations between nodes.

Shared data 345 may exist in volatile memory 320 and/or memory storage315 as a type of data exchanged between nodes. For example, context data(such as environmental data) may be a type of shared data 345.

Sensor data 350 may also exist in volatile memory 320 and/or memorystorage 315 as a type of data recorded and collected from an onboardsensor or from another node. For example, sensor data 350 may includetemperature readings from a temperature sensor onboard an ID node and/orhumidity readings from a humidity sensor in another ID node (e.g., fromanother of the ID nodes within container 210 as shown in FIG. 2).

Thus, an ID node (such as node 120 a shown in FIG. 3) is a lower costwireless node that communicates with other ID nodes and master nodes viaa short-range radio with variable RF characteristics, can be associatedwith other nodes, can broadcast to and scan for other nodes, associatedwith other nodes, and store/exchange information with other nodes.

Master Node

A master node, such as master node 110 a shown in more detail in FIG. 4,shares many ID node features but generally expands upon them in order tofunction as a bridge to the server 100. In general, while an ID node isa type of lower level node in an exemplary wireless node network, amaster node is a type of higher level node. An exemplary master node maybe in a fixed location or otherwise stationary, while other examplemaster nodes may be implemented as movable and mobile devices.

Referring now to FIG. 4, exemplary master node 110 a comprises aprocessing or logic unit 400 coupled to a short-range communicationinterface 480, memory storage 415, volatile memory 420, clock/timer 460,and battery/power interface 470. In some embodiments, the short-rangecommunication interface 480 may have variable power characteristics,such as receiver sensitivity and RF output power level. Those skilled inthe art will appreciate that processing unit 400 is logic, such as amicroprocessor or microcontroller, which generally performs computationson data and executes operational and application program code and otherprogram modules within the master node 110 a.

In general, those skilled in the art will appreciate that thedescription of hardware with respect to ID node 110 a in FIG. 4 appliesto the similar hardware and software features appearing in each type ofnode, including a master node. Those skilled in the art will appreciatethat exemplary master node 110 a is a hardware-based component that mayimplement processor 400 with a single processor or logic unit, a morepowerful multi-core processor, or multiple processors depending upon thedesired implementation. In one embodiment, processing unit 400 may beimplemented with a low power microprocessor and associated peripheralcircuitry. Less complex microcontrollers or discrete circuitry may beused to implement processing unit 400 as well as more complex andsophisticated general purpose or dedicated purpose processors.

In yet another embodiment, exemplary processing unit 400 may beimplemented by a low power ARM1176JZ-F application processor used aspart of a single-board computer, such as the Raspberry Pi Computer ModelB-Rev-2. The ARM application processor is embedded within a Broadcom®BCM2835 system-on-chip (SoC) deployed in the Raspberry Pi Computer. Inthis embodiment, the Raspberry Pi Computer device operates as a core ofexemplary master node 110 a and includes a Secure Digital memory cardslot and flash memory card operating as memory storage 415, a 512 MbyteRAM memory storage operating as volatile memory 420, an operating system(such as Linux) stored on memory storage 415 and running in volatilememory 420, and peripherals that implement clock/timer 460, and a powersupply operating as a power interface 470.

Like short-range interface 375 in ID node 120 a, exemplary master node110 a includes a short-range communication interface 480 as aprogrammable radio and an omni-directional antenna coupled to theprocessing unit 400. In some embodiments, the short-range communicationinterface 480 may have variable RF power characteristics, such asreceiver sensitivity and/or RF output signal power level. In someembodiments, interface 480 may use an antenna with a different antennaprofile when directionality may be desired. Examples of short-rangecommunication interface 480 may include other hardware (not shown) foroperatively coupling the device to a specific short-range communicationpath (e.g., a Bluetooth® Low Energy (BLE) connection path communicatingat 2.4 GHz). While BLE is used in one embodiment to enable a short-rangecommunication protocol, variable power short-range interface 480 may beimplemented with other low power, short-range communication protocols,such as ultra-low power communication protocols used with ultra-widebandimpulse radio communications, ZigBee protocols, IEEE 802.15.4 standardcommunication protocols, and the like.

In one embodiment, various RF characteristics of the radio'stransceiver, such as the RF output power and the RF receiver sensitivitymay be dynamically and programmatically varied under control ofprocessing unit 400. In other embodiments, further RF characteristics ofthe radio's transceiver may be programmatically varied, such asfrequency, duty cycle, timing, modulation schemes, spread spectrumfrequency hopping aspects, etc., as needed to flexibly adjust the RFoutput signal as needed depending upon a desired implementation andanticipated use of exemplary master node 110 a. In other words,embodiments of master node 110 a (or any other master node) may haveprogrammatically adjustable RF characteristics (such as an adjustable RFoutput signal power, an adjustable RF receiver sensitivity, the abilityto switch to a different frequency or frequency band, etc.).

In addition to the short-range communication interface 480, exemplarymaster node 110 a includes a medium and/or long-range communicationinterface 485 to provide a communication path to server 100 via network105. Those skilled in the art will appreciate that in some embodiments,an exemplary communication interface deployed may be considered toembody a short-range communication interface (such as interface 480) ora medium/long range communication interface (such as interface 485).However, in more general embodiments, reference to a communicationinterface may include an interface that collectively implements aplurality of different exemplary data communication interfaces whilestill being generally referenced as “a communication interface” or“wireless communication interface.”

In one embodiment, communication interface 485 may be implemented with amedium range radio in the form of an IEEE 802.11g compliant WiFitransceiver. In another embodiment, communication interface 485 may beimplemented with a longer range radio in the form of a cellular radio.In yet another embodiment, both a WiFi transceiver and a cellular radiomay be used when best available or according to a priority (e.g., firstattempt to use the WiFi transceiver if available due to possible lowercosts; and if not, then rely on the cellular radio). In other words, anembodiment may rely upon the longer range cellular radio part ofinterface 485 as an alternative to the medium range WiFi transceiverradio, or when the medium range radio is out of reach from a connectinginfrastructure radio within network 105. Thus, in these embodiments,medium and/or long-range communication interface 485 may be used tocommunicate captured node information (e.g., profile data 430,association data 440, shared data 445, sensor data 450, and locationdata 455) to server 100.

The battery/power interface 470 for master node 110 a generally powersthe circuitry implementing master node 110 a. In one embodiment,battery/power interface 470 may be a rechargeable power source. Forexample, a master node may have a rechargeable power source along with asolar panel that charges the power source in order to help facilitatedeployment of the master in a remote location. In another embodiment,battery/power interface 470 may be a non-rechargeable power sourceintended to be disposed of after use. In yet another embodiment,battery/power interface 470 may be a power interface connector (such asa power cord and internal power supply on master node 110 a). Thus, whenan exemplary master node is in a fixed or stationary configuration, itmay be powered by a power cord connected to an electrical outlet, whichis coupled to an external power source. However, other mobile masternodes may use an internal power source, such as a battery.

The clock/timer 460 for master node 110 a generally provides one or moretiming circuits used in, for example, time delay, pulse generation, andoscillator applications. In an embodiment where master node 110 aconserves power by entering a sleep or dormant state for a predeterminedtime period as part of overall power conservation techniques,clock/timer 460 assists processing unit 400 in managing timingoperations.

Optionally, an embodiment may also implement master node 110 a asincluding one or more sensors 465 (similar to sensors deployed on IDnode based Sensor nodes and described above with respect to FIG. 3).Additionally, an embodiment of master node 110 a may also provide a userinterface 405 to indicate status, allow basic interaction for review ofcaptured node data and interaction with nodes and server 100 (such asviewing of notifications). In one embodiment, user interface 405 mayprovide a display, interactive buttons or soft keys, and a pointingdevice to facilitate interaction with the display. A notification oralert may be generated by master node 110 a and shown on the display, onin other embodiments, the notification or alert may be received bymaster node 110 a from another node (e.g., an ID node, another masternode, and/or a server) and shown on the display. In a furtherembodiment, a data entry device may also be used as part of the userinterface 405. In other embodiments, user interface 405 may take theform of one or more lights (e.g., status lights), audible input andoutput devices (e.g., a microphone and speaker), or touchscreen.

As previously noted, an exemplary master node, such as master node 110a, may be positioned in a known fixed location or, alternatively,includes dedicated location positioning circuitry 475 (e.g., GPScircuitry) to allow the master node self-determine its location or todetermine its location by itself. In other embodiments, alternativecircuitry and techniques may be relied upon for location circuitry 475(rather than GPS), such as location circuitry compatible with othersatellite-based systems (e.g., the European Galileo system, the RussianGLONASS system, the Chinese Compass system), terrestrial radio-basedpositioning systems (e.g., cell phone tower-based or WiFi-basedsystems), infrared positioning systems, visible light based positioningsystems, and ultrasound-based positioning systems).

Regarding memory storage 415 and volatile memory 420, both areoperatively coupled to processing unit 400 in exemplary master node 110a. Both memory components provide program elements used by processingunit 400 and maintain and store data elements accessible to processingunit 400 (similar to the possible data elements stored in memory storage315 and volatile memory 320 for exemplary ID node 120 a).

In the embodiment shown in FIG. 4, memory storage 415 maintains avariety of executable program code (e.g., master control and managementcode 425), data similar to that kept in an ID node's memory storage 315(e.g., profile data 430, security data 435, association data 440, shareddata 445, sensor data 450, and the like) as well as other data morespecific to the operation of master node 110 a (e.g., location data 455that is related to the location of a particular node). Like memorystorage 315, memory storage 415 is a tangible, non-transient computerreadable medium on which information (e.g., executable code/modules,node data, sensor measurements, etc.) may be kept in a non-volatile andnon-transitory manner.

Like volatile memory 320 in ID node 120 a, volatile memory 420 istypically a random access memory (RAM) structure used by processing unit400 during operation of the master node 110 a. Upon power up of masternode 110 a, volatile memory 120 may be populated with an operationalprogram (such as master control and management code 425) or specificprogram modules that help facilitate particular operations of masternode 110 a. And during operation of master 110 a, volatile memory 420may also include certain data (e.g., profile data 430, security data435, association data 440, shared data 445, sensor data 450, and thelike) generated as the master node 110 a executes instructions asprogrammed or loaded from memory storage 415.

Master Control & Management Code

Generally, an embodiment of master control and management code 425 is acollection of software features implemented as programmatic functions orprogram modules that generally control the behavior of a master node,such as master node 110 a. In one embodiment, master control andmanagement code 425 generally comprises several programmatic functionsor program modules including (1) a node advertise and query (scan) logicmanager, which manages how and when a node communicates; (2) aninformation control and exchange manager, which manages whether and howinformation may be exchanged between nodes; (3) a node power manager,which manages power consumption and aspects of RF output signal powerand/or receiver sensitivity for variable short-range communications; (4)an association manager focusing on how the node associates with othernodes; (5) a location aware/capture module to determine node location;(6) a delivery release control module; and (7) a delivery notificationmodule.

Master Node Program Modules and ID Node Modules

In an exemplary embodiment, program modules (1)-(4) of master nodecontrol and management code 425 generally align with the functionalityof similarly named program modules (1)-(4) of node control andmanagement code 325 as described above with respect to FIG. 3.Additionally, as node control and management code 325 may also comprisean airborne mode program module, those skilled in the art willappreciate and understand that master node control and management code425 may also comprise a similar functionality airborne mode programmodule in order to allow advantageous operations of a master node whileairborne. However, and consistent with examples set forth below, suchmodules may have some differences when in a master node compared withthose controlling an ID node.

Location Aware/Capture Module

In addition to exemplary program modules (1)-(4) of code 425, anexemplary embodiment of master node control and management code 425 willfurther comprise an exemplary location aware/capture module related tonode location (more generally referred to as a location manager modulefor a master node). In general, the exemplary location aware/capturemodule deployed in an exemplary master node may determine its ownlocation and, in some embodiments, the location of a connected node.Embodiments of the exemplary location aware/capture module may work inconjunction with location manager program code residing and operating ina server (e.g., as part of server control and management code 525) whendetermining node locations of other nodes, as discussed in more detailherein.

In one embodiment, a master node may be positioned in a known, fixedlocation. In such an embodiment, the exemplary location aware/capturemodule may be aware that the master node location is a known, fixedlocation, which may be defined in a fixed, preset, or preprogrammed partof memory storage 415 (e.g., information in the location data 455maintained in memory storage 415). Examples of such location informationmay include conventional location coordinates or other descriptivespecifics that identify the location of the master node. In anotherembodiment where the master node may not be inherently known or a fixedlocation at all times (e.g., for a mobile master node), the exemplarylocation aware/capture module may communicate with location circuitry,such as GPS circuitry 475 on a master node, to determine the currentlocation of the master node.

In an embodiment, the location of the master node may be communicated tothe server, which may use this location information as part of managingand tracking nodes in the wireless node network. For example, if anexemplary master node is mobile and has determined a new currentlocation using location circuitry 475, the master node may provide thatnew current location for the master node to the server. Additionally,when the master node's exemplary location aware/capture moduledetermines the location of a node associated with the master node, themaster node may also provide the location of that node associated withthe master node to the server.

An exemplary embodiment of master node control and management code 425may also comprise an exemplary delivery release control module thatenhances delivery management with certain types of master nodes. Forexample, as explained in more detail below, an embodiment of a masternode maybe part of an exemplary logistics receptacle that stores an itemthat may be shipped. Such a logistics receptacle may maintain the itemwithin its storage area in a secure manner and execute the deliveryrelease control module to help manage delivery to selectively releasethe item under certain conditions to make sure the item is properlydelivered and help avoid unintentional deliveries to an incorrectlocation. Embodiments of the exemplary delivery release control modulemay work in conjunction with the location aware/capture module andlocation manager program code residing and operating in a server (e.g.,as part of server control and management code 525) when determining nodelocations of other nodes, as discussed in more detail herein.

In a further embodiment, master node control and management code 425 mayalso comprise an exemplary delivery notification module that, ingeneral, generates a corrective delivery or pickup notification withcertain types of master nodes to help proactively notify relevantlogistics personnel about a delivery or pickup, respectively. Asexplained in more detail below, an embodiment of a mobile master node(such as a courier master node) may automatically sense an adversedelivery/pickup condition as, for example, a sensed incorrect locationfor delivery/pickup of an item, movement away from an intendeddelivery/pickup location for the item, or a time-based factor (e.g., adesired delivery window) combined with the intended delivery location.In another embodiment, an exemplary master node associated with alocation (as opposed to a mobile courier master node) may automaticallysense such an adverse delivery/pickup condition and transmit acorrective delivery/pickup notification to the courier master node as away of proactively rectifying the delivery/pickup situation involvingthe sensed adverse delivery/pickup condition (such as when the item isdropped off at an incorrect location, an item is not dropped off and isheading away from the intended delivery location, the wrong item ispickup up, the item is not picked up, and messaging with the couriermaster node may help quickly resolve such issues). Embodiments of theexemplary delivery notification module may work in conjunction with thelocation aware/capture module and location manager program code residingand operating in a server (e.g., as part of server control andmanagement code 525) when determining node locations of other nodes(such as an ID node associated with an item delivered at or picked upfrom a master node's location or heading away from the master node'slocation), as discussed in more detail herein.

In a further embodiment, master node control and management code 425 mayalso comprise an exemplary pickup notification module that, in general,generates a pickup notification related to an inventory item as part ofmonitoring the item as it is within inventory and, in some instances, asthe item is authorized for release and entry into a shipment operation.As explained in more detail below, an embodiment of an exemplary masternode associated with a particular location (such as warehouse or, moregenerally, a storage facility) may generate the pickup notification whenthe inventory item should not be leaving the location. Embodiments ofthe exemplary pickup notification module may also work in conjunctionwith the location aware/capture module and location manager program coderesiding and operating in a server (e.g., as part of server control andmanagement code 525) when determining node locations of other nodes(such as an ID node associated with an inventory item maintained as partof the location's inventory), as discussed in more detail herein.

Server

While FIGS. 3 and 4 illustrate details of hardware and software aspectsof an exemplary ID node and exemplary master node, respectively, FIG. 5provides a more detailed diagram of an exemplary server that may operateas part of an exemplary wireless node network in accordance with anembodiment of the invention. In an exemplary embodiment, server 100 maybe referred to as an Association and Data Management Server (ADMS) thatmanages the nodes, collects information from the nodes, stores thecollected information from the nodes, maintains or has access to contextdata related to the environment in which the nodes are operating, andmay provide information about the nodes (e.g., status, sensorinformation, etc.) to requesting entities. Further details on variousembodiments that take advantage of this functionality are explainedbelow. Those skilled in the art will appreciate that node density,geographic installation characterization, and network connectively areall types of examples of factors that may impact a final architecturedesired for an embodiment of a wireless node network.

Referring now to FIG. 5, exemplary server 100 is shown as a networkedcomputing platform capable of connecting to and interacting with atleast the wireless master nodes. In other embodiments, exemplary server100 is also capable of connecting to and interacting with one or moreuser access devices. Those skilled in the art will appreciate thatexemplary server 100 is a hardware-based component that may beimplemented in a wide variety of ways. For example, server 100 may use asingle processor or may be implemented as one or more part of amulti-processor component that communicates with devices (such as useraccess devices 200, 205) and wireless nodes (such as master node 110 a).

In general, those skilled in the art will further appreciate that server100 may be implemented as a single computing system, a distributedserver (e.g., separate servers for separate server related tasks), ahierarchical server (e.g., a server implemented with multiple levelswhere information may be maintained at different levels and tasksperformed at different levels depending on implementation), or a serverfarm that logically allows multiple distinct components to function asone server computing platform device from the perspective of a clientdevice (e.g., devices 200, 205 or master node 110 a). In some regionaldeployments, an exemplary server may include servers dedicated forspecific geographic regions as information collected within differentregions may include and be subject to different regulatory controls andrequirements implemented on respective regional servers.

Likewise, while the embodiment shown in FIG. 5 illustrates a singlememory storage 515, exemplary server 100 may deploy more than one memorystorage media. And memory storage media may be in differingnon-transitory forms (e.g., conventional hard disk drives, solid statememory such as flash memory, optical drives, RAID systems, cloud storageconfigured memory, network storage appliances, etc.).

At its core, exemplary server 100 shown in FIG. 5 comprises a processingor logic unit 500 coupled to a network interface 590, which facilitatesand enables operative connections and communications through network 105with one or more master nodes as well as, in some embodiments, useraccess devices, such as devices 200, 205. In one embodiment, server 100may include a medium and/or long-range communication interface 595 withwhich to more directly communicate with one or more master nodes. Usingthese communication paths as well as program code or program modules(such as server control and management code 525), the server 100generally operates to coordinate and manage information related to an IDnode as an item associated with the ID node physically moves from onelocation to another.

As a computing platform, the processing unit 500 of exemplary server 100is operatively coupled to memory storage 515 and volatile memory 520,which collectively store and provide a variety of executable programcode (e.g., server control and management code 525), data similar tothat kept in a master or ID node's respective memory storage (e.g.,profile data 530, security data 535, association data 540, shared data545, sensor data 550, location data 555) and context data 560 related tothe environment in which the nodes are operating (e.g., informationgenerated from within the wireless node network and information createdexternal to the wireless node network).

Like memory storage 315 and storage 415, memory storage 515 is atangible, non-transient computer readable medium on which information(e.g., executable code/modules (e.g., server control and management code525), node-related data (e.g., profile data 530, security data 535,association data 540, location data 555, etc.), measurement information(e.g., a type of shared data 545, sensor data 550, etc.), andinformation on the contextual environment for the nodes (e.g., contextdata 560) may be kept in a non-volatile and non-transitory manner.

Those skilled in the art will appreciate that the above identificationof particular program code and data are not exhaustive and thatembodiments may include further executable program code or modules aswell as other data relevant to operations of a processing-based device,such as an ID node, a master node, and a server.

Context Data

As noted above, server 100 may access context data 560 as part ofmanaging nodes in the wireless node network. The exemplary server 100may contain a collection of such context data 560 in a context database565 according to an embodiment. As illustrated in FIG. 5, exemplarycontext database 565 is a single database accessible by processing unit500 internal to server 100. Those skilled in the art will readilyunderstand that other configurations that provide an accessiblecollection of context data 560 are possible and contemplated within thescope and principles of embodiments of the invention. For example,context database 565 may be an externally accessible database (ormultiple databases), such as an accessible storage maintained outsidethe server 100 via a dedicated interface or a network storage device (ornetwork attached storage (NAS) unit). In yet another embodiment, thecontext database may be separately maintained by an external databaseserver (not shown) that is distinct from server 100, but accessiblethrough a communication path from server 100 to a separate databaseserver (e.g., via network 105). Furthermore, those skilled in the artwill appreciate that context database 565 may be implemented with cloudtechnology that essentially provides a distributed networked storage ofcollections of information (such as context data 560, sensor data 550,shared data 545, etc.) accessible to server 100.

Within context database 565, an exemplary embodiment of the collectionof context data 560 may be maintained that generally relates to anenvironment in which the nodes are operating or anticipated to beoperating. In more detail, the context data 560 may generally relate towhat a similar node has experienced in a similar environment to what agiven node is presently experiencing or is anticipated to experience asthe given node moves.

In a general example, an environment in which a node may be actually oranticipated to be operating may include different types ofenvironments—for example, an electronic communication environment (e.g.,an RF environment that may be cluttered with signals or includematerials or structure that may impede or otherwise shield RFcommunications), a physical environment of an anticipated path alongwith the identified node moves (e.g., temperature, humidity, security,and other physical characteristics), a conveyance environment related tohow a node may move or be anticipated to be moving (e.g., speed andother parameters of a truck, airplane, conveyor system), and a densityenvironment related to the density of nodes within an area near aparticular node (e.g., how many nodes are anticipated to occupy acorridor, such as structure 2200 shown in FIG. 22A, or a storagefacility through which a particular ID node is anticipated to transit onits shipping path).

In light of these different aspects of a node's operating environment,exemplary context data 560 may provide information related to differentstructures and conditions related to movement of an item (e.g., aparticular type of courier device, vehicle, facility, transportationcontainer, etc.). Such information may be generated by an entityoperating the wireless node network, such as a shipping company.Additionally, exemplary context data 560 may include third party datagenerated external to the wireless node network. Thus, context data,such as data 560, may include a wide variety of data that generallyrelates to the environment in which the nodes are operating and may beused to advantageously provide enhanced node management capabilities inaccordance with embodiments of the present invention.

In general, FIG. 5 illustrates exemplary types of context data 560 beingmaintained in database 565 and in volatile memory 520. Those skilled inthe art will appreciate that context data 560 may also be maintained inother data structures, in addition to or instead of maintaining suchinformation in a database. As illustrated in FIG. 5, exemplary types ofcontext data 560 may include but are not limited to scan data 570,historic data 575, shipment data 580, layout data 585, RF data 587, and3^(rd) party data.

Scan data 570 is generally data collected for a particular item relatedto an event. For example, when an item is placed in a package (such aspackage 130), a label may be generated and placed on the exterior of thepackage. The label may include a visual identifier that, when scanned byan appropriate scanning device capable of capturing, identifies thepackage. The information generated in response to scanning theidentifier (a type of event), may be considered a type of scan data.Other scan data 570 may include, for example, general inventory datagenerated upon manual entry of information related to the package;captured package custodial control data; and bar code scan data.

Historic data 575 is generally data previously collected and/or analyzedrelated to a common characteristic. Historic data 575 embodiesoperational knowledge and know-how for a particular characteristicrelevant to operations of the wireless node network. For example, thecommon characteristic may be a particular event (e.g., movement of anitem from an open air environment to within a particular closedenvironment, such as a building), a type of item (e.g., a type ofpackage, a type of content being shipped, a location, a shipment path,etc.), a success rate with a particular item (e.g., successfulshipment), and the like. Another example of historic data 575 mayinclude processing information associated with how an item has beenhistorically processed as it is moved from one location to another(e.g., when moving within a particular facility, processing informationmay indicate the item is on a particular conveyor and may includeinformation about the conveyor (such as speed and how long it isanticipated the item will be on the conveyor)).

Shipment data 580 is generally data related to an item being moved fromone location to another location. In one embodiment, shipment data 580may comprise a tracking number, content information for an item beingshipped, address information related to an origin and destinationlocations, and other characteristics of the item being moved.

Layout data 585 is generally data related to the physical area of one ormore parts of an anticipated path. For example, an embodiment of layoutdata 585 may include building schematics and physical dimensions ofportions of a building in which a node may be transiting. An embodimentmay further include density information associated with physical areasto be transited and anticipated numbers of potential nodes in thoseareas as types of layout data. In another example, an embodiment oflayout data may include a configuration of how a group of packages maybe assembled on a pallet, placed into a shipping container (e.g., a unitload device (ULD)) that helps move a collection of items on variousforms with single mode or intermodal transport.

RF data 587 is generally signal degradation information about a signalpath environment for a particular type of node and may relate toparticular adverse RF conditions that may cause signal fluctuations,interference, or other degradation from the otherwise optimal signalpath environment for that type of node. For example, RF data may includeshielding effects when using a particular packaging or location,shielding effects when the package is within a particular type ofcontainer or assembled as part of a palletized shipment, shieldingeffects when particular content is shipped, and other physical andelectronic interference factors.

Third party data 589 is an additional type of context data 560 thatgenerally includes data generated outside the network. For example,third party data may include weather information associated withparticular areas to be transited as the item is moved along ananticipated path from one location to another. Those skilled in the artwill appreciate other types of third party data that relate to physicaland environmental conditions to be faced by an item being moved from onelocation to another may also be considered context data 560.

The use of context data, such as context data 560 described above,advantageously helps server 100 better manage movement of items, providebetter location determination, enhance intelligent operation andmanagement of different levels of the wireless node network, and provideenhanced visibility to the current location and status of the itemduring operation of the wireless node network. In one embodiment, servercontrol and management code 525 may provide such functionality thatenables the wireless node network to be contextually aware andresponsive.

Server Control & Management Code

Generally, server control and management code 525 controls operations ofexemplary server 100. In an embodiment, server control and managementcode 525 is a collection of software features implemented asprogrammatic functions in code or separate program modules thatgenerally control the behavior of server 100. Thus, exemplary servercontrol and management code 525 may be implemented with severalprogrammatic functions or program modules including, but not limited to,(1) a server-side association manager, which provides a framework formore robust and intelligent management of nodes in the wireless nodenetwork; (2) a context-based node manager, which enhances management ofnodes in the wireless node network based upon context data; (3) asecurity manager, which manages secure pairing aspects of nodemanagement; (4) a node update manager, which provides updated ordifferent programming for a particular node and shares information withnodes; (5) a location manager for determining and tracking the locationof nodes in the network; and (6) an information update manager, whichservices requests for information related to the current status of anode or generally providing information about a node or collected from anode.

Server-Side Association Manager

The server-side association manager (also referred to as a server-sideassociation management function) is generally a program module inexemplary code 525 that is responsible for intelligently managing thenodes in the wireless node network using a secure information framework.In an embodiment, this framework may be implemented to be acontext-driven, learning sensor platform. The framework may also enablea way for information (such as RF scan, location, date/time, and sensordata) to be securely shared across nodes, a way to change the behaviorof a node, and for a node to know it is considered “missing.” Theframework established during operation of the server-side associationmanager allows the network of nodes to be managed as a system withenhanced and optimized accuracy of determining the physical location ofeach ID Node. Further information regarding particular embodiments ofsuch an association management framework and methods are explained belowin more detail.

Context-Based Association Manager

The context-based node manager is generally a program module inexemplary code 525 that is responsible for incorporating context data aspart of management operations to provide an enhanced data foundationupon which visibility of the nodes may be provided. In some embodiments,the context-based node manager may be implemented as part of theserver-side association manager while other embodiments may implementthe context-based node manager as a separate program module.

In one embodiment, the enhanced data foundation relies upon contextdata, such as context data 560 (e.g., scan data 570, historic data 575,shipment data 580, layout data 585, and other third party contextualdata providing information regarding the conditions and environmentsurrounding an item and ID node moving from one location to another.Such context data (e.g., the network know-how, building layouts, andoperational knowledge of nodes and shipping paths used with the wirelessnode network) may provide the enhanced building blocks that allow theserver 100 to manage tracking and locating of nodes in a robustlyenriched contextual environment. In an embodiment, context-basedmanagement provides visibility to the system through data analysis forwhen and how associations should be expected as the nodes travel throughthe wireless node network. In other embodiments, it may provide thefoundation for better understanding RF signal degradation, which can becaused by the operating environment, packaging, package content, and/orother packages related to an item and its ID node.

Security Manager

The security manager module, which may be implemented separately or aspart of the association manager module in exemplary server control andmanagement code 525, helps with associating two nodes in the wirelessnode network by managing aspects of secure pairing of the nodes. In oneembodiment, security manager module provides the appropriate pairingcredentials to allow a node to securely connect to another node. Thus,when a node desires to connect to another node, an embodiment requiresappropriate pairing credentials be generated by the server, provided tothe nodes, and observed within the nodes to allow for a successfulconnection or association of nodes.

In operation, a node (such as master node 110 a) identifies the addressof the node (such as ID node 120 a) to whom it desires to connect. Withthis address, the node prepares a pairing request and sends the requestto the server 110. The server 100 operates under the control of thesecurity manager module of the association manager, and determineswhether the requesting node should be connected or otherwise associatedwith the other node. If not, the server does not issue the requestedsecurity credentials. If so and in accordance with the desiredassociation management paradigm set by the association manager of code525, server provides the requested credentials necessary for asuccessful wireless pairing and the establishment of securecommunications between the associated nodes.

Node Update Manager

The exemplary server control and management code 525 may include a nodeupdate manager module that provides updated programming information tonodes within the wireless node network and collects information fromsuch nodes (e.g., shared data 545, sensor data 550). The node updatemodule may be implemented separately or as part of the associationmanager module in exemplary server control and management code 525.

Providing an update to a node's programming may facilitate and enabledistribution of node functions to save power and better manage the nodesas a system. For example, one embodiment may alter the functionalresponsibility of different nodes depending on the context orassociation situation by temporarily offloading responsibility for aparticular function from one node to another node. Typically, the serverdirects other nodes to change functional responsibility. However, insome embodiments, a master node may direct other nodes to alterfunctional responsibility.

Sharing information between nodes and with server (e.g., via anexemplary node update manager) facilitates collecting information from anode and sharing information with other nodes as part of an associationmanagement function of server 100. For example, one embodiment maycollect and share RF scan data (a type of shared data 545), informationabout a node's location (a type of location data 555), systeminformation about date/time (another type of shared data 545), andsensor measurements collected from sensor nodes (a type of sensor data550).

Location Manager

The exemplary server control and management code 525 may include alocation manager module that helps determine and track node locations.In a general embodiment, the location of a node may be determined by thenode itself (e.g., a master node's ability to determine its own locationvia location circuitry 475), by a node associated with that node (e.g.,where a master node may determine the location of an ID node), by theserver itself (e.g., using location information determined by one ormore techniques implemented as part of code 525), and by a combinedeffort of a master node and the server.

In general, an exemplary ID node may be directly or indirectly dependenton a master node to determine its actual physical location. Embodimentsmay use one or more methodologies to determine node location. Forexample and as more specifically described below, possible methods fordetermining node location may relate to controlling an RF characteristicof a node (e.g., an RF output signal level and/or RF receiversensitivity level), determining relative proximity, consideringassociation information, considering location adjustments for contextinformation and an RF environment, chaining triangulation, as well ashierarchical and adaptive methods that combine various locationmethodologies. Further information and examples of how an exemplarylocation manager module may determine a node's location in accordancewith such exemplary techniques are provided in more detail below.

Additionally, those skilled in the art will appreciate that it may alsobe possible to determine what constitutes an actionable location versusactual location based upon contextual information about the item beingtracked. For example, a larger item may require relatively less locationaccuracy than a small item such that operational decisions and statusupdates may be easier implemented with knowledge of context. If the sizeof the item is known, the location accuracy can be tuned accordingly.Thus, if a larger item is to be tracked, or if the system's contextualawareness of it is such that lower location accuracy can be used, astronger signal and thus wider area of scanning may be employed, whichmay help in situations where RF interference or Shielding is an Issue.

Information Update Manager

The exemplary server control and management code 525 may include aninformation update manager module that provides information related tooperations of the wireless node network and status of nodes. Suchinformation may be provided in response to a request from a deviceoutside the wireless node network (such as user access device 200). Forexample, someone shipping an item may inquire about the current statusof the item via their laptop or smartphone (types of user accessdevices), which would connect to server 100 and request suchinformation. In response, the information update manager module mayservice such a request by determining which node is associated with theitem, gathering status information related to the item (e.g., locationdata, etc.), and provide the requested information in a form that istargeted, timely, and useful to the inquiring entity.

In another example, a user access device may connect to server 100 andrequest particular sensor data from a particular node. In response,information update manager may coordinate with node update manager, andprovide the gathered sensor data 545 as requested to the user accessdevice.

Node Filtering Manager

An embodiment of exemplary server control and management code 525 mayoptionally comprise a node filtering manager, which helps manage thetraffic of nodes with a multi-level filtering mechanism. The filteringessentially sets up rules that limit potential associations andcommunications. An example of such a node filtering management maydefine different levels or modes of filtering for a master node (e.g.,which ID nodes can be managed by a master node as a way of limiting thecommunication and management burdens on a master node).

In one example, a “local” mode may be defined where the ID node onlycommunicates and is managed by the assigned master node at the locationwhere the last wireless node contact back to server 100 and/or wherethird party data indicates the assigned master node and ID node are inphysical and wireless proximity. Thus, for the “local” mode of trafficfiltering, only the assigned master node communicates and processesinformation from a proximately close and assigned ID node.

Moving up to a less restrictive filtering mode, a “regional” mode offiltering may be defined where the ID node may communicate and bemanaged by any master node at the location last reported back to server100 and/or where third party data indicates the ID node is located.Thus, for the “regional” mode of traffic filtering, any master node nearthe ID node may communicate and process information from that ID node.This may be useful, for example, when desiring to implement a limit onassociations and pairings to within a particular facility.

At the least restrictive filtering mode, a “global” mode of filteringmay be defined as essentially system-wide communication where the IDnode may be allowed to communicate and be managed by any master node. Inother words, the “global” mode of traffic filtering allows any ID nodewithin the wireless node network to communicate information through aparticular master node near the ID node may communicate and processinformation from that ID node.

Thus, with such exemplary filtering modes, an ID node in a certaincondition (e.g., distress, adverse environmental conditions, adverseconditions of the node, etc.) may signal the need to bypass anyfiltering mechanism in place that helps manage communications andassociation by using the “Alert” Status Flag. In such an example, thiswould operate to override any filtering rules set at the Master Nodelevel in order to allow an ID node to be “found” and connect to anothernode.

Thus, exemplary server 100 is operative, when executing code 525 andhaving access to the types of data described above, to manage the nodes,collect information from the nodes, store the collected information fromthe nodes, maintain or have access to context data related to theenvironment in which the nodes are operating, and provide informationabout the nodes (e.g., status, sensor information, etc.) to a requestingentity.

Node Communication & Association Examples

To better illustrate how exemplary management and communicationprinciples may be implemented within an exemplary wireless node network,FIGS. 8-12 provide several examples of how exemplary components of thewireless node network may generally communicate (advertising &scanning), associate, and exchange information during different types ofoperations in various embodiments. FIGS. 22A-C also provide a moredetailed application of such exemplary association and communicationactivities when an exemplary ID node moves along a transit path (e.g.,through a corridor) and is tracked and managed by different master nodesand a server in an embodiment.

Node Advertising Cycle Example

As generally explained above, a node may have several different types ofadvertising states in which the node may be connectable with other nodesand may communicate with other nodes. And as a node moves within awireless node network, the node's state of advertising and connectionmay change as the node disassociates with a previously connected node,associates with a new node, or finds itself not associated with othernodes. In some situations, a node may be fine and in normal operationnot be connected or associated with another node. However, in othersituations, a node may raise an issue with potentially being lost if ithas not connected with any other node in a very long period of time. Assuch, a node may go through different types of advertising states inthese different operational situations.

Generally, a node may be in a state where it is not connectable withother nodes for a certain period of time (also referred to as anon-connectable interval). But later, in another state, the node maywant to be connected and advertises as such for a defined connectableperiod (also referred to as a connectable interval). As the nodeadvertises to be connected, the node may expect to be connected at somepoint. In other words, there may be a selectable time period withinwhich a node expects to be connected to another node. However, if thenode is not connected to another node within that period of time(referred to as an Alert Interval), the node may need to take specificor urgent action depending upon the circumstances. For example, if anode has not been connected to another node for 30 minutes (e.g., anexample alert interval), the node may change operation internally tolook “harder” for other nodes with which to connect. More specifically,the node may change its status flag from an Alert Level 0 (no issue,operating normal) to Alert Level 2 in order to request that anyavailable master node acknowledge receipt of the advertisement packetbroadcasted by the node seeking a connection.

FIG. 8 is a diagram illustrating exemplary advertising states (orinformation exchange and node connectability states) and factorsinvolved in transitions between the states by an exemplary ID node in awireless node network in accordance with an embodiment of the invention.Referring now to FIG. 8, three exemplary states for a node areillustrated as part of an exemplary advertising cycle for thenode—namely, an ID Node Non-Connectable Advertising state 805, an IDNode Discoverable Advertising state 815, and an ID Node GeneralAdvertising state 830. Transitions between these states will depend onfactors related to expirations of the types of intervals describedabove. In an embodiment, the duration of each of these intervals willdepend upon the system implementation and the contextual environmentwithin which the ID node is operating. Such time intervals may, forexample, be set by server 100 as part of data (e.g., profile data,association data, context data) provided to the node when updating thenode and managing operations of the node.

Referring to the example illustrated in FIG. 8, an exemplary ID node mayhave an alert interval set at, for example, 30 minutes, and be in IDNode Non-Connectable Advertising state 805 with a non-connectableinterval set at 5 minutes. In state 805, the ID node may broadcast oradvertise, but is not connectable and will not receive a SCAN_REQmessage (a type of request for more information sent to the advertisingnode from another node). Thus, the ID node in state 805 in this examplemay advertise in a non-connectable manner for at least 5 minutes butexpects to be connected within 30 minutes.

If the alert interval has not yet elapsed (factor 810) and thenon-connectable interval is still running (factor 825), the ID nodesimply stays in state 805. However, if the alert interval has notelapsed (factor 810) and the non-connectable interval elapses (factor825), the ID node will enter a mode where it wants to try to connect toanother node for a period of time (e.g., a 1 minute connectableinterval) and will move to the ID Node General Advertising state 830 inthe exemplary advertising cycle of FIG. 8. In state 830, as long as theconnectable interval is running, the ID node will stay in this statewhere it is connectable to another node and will receive SCAN_REQ typesof requests from other nodes in response to the advertising packets theID node is broadcasting. However, when the connectable interval (e.g.,the 1 min period) elapses or expires (factor 835), the ID node returnsback to the Non-connectable Advertising state 805 for either the nexttime the non-connectable interval elapses (and the ID node again triesto connect in state 830) or the alert interval finally elapses (and theID node finds itself in a situation where it has not connected toanother node despite its efforts to connect in state 830).

When the alert interval finally elapses (factor 810), the ID node movesto the ID Node Discoverable Advertising state 815. Here, the ID node isnot yet connectable but will receive a SCAN_REQ type of request fromother nodes in response to advertising packets the ID node isbroadcasting. In this state 815, the exemplary ID node may alter itsstatus flag to indicate and reflect that its alert interval has expiredand that the node is now no longer in normal operation. In other words,the ID node may change the status flag to a type of alert status beingbroadcasted to indicate the ID node urgently needs to connect withanother node. For example, the status flag of the advertising packetbroadcast by the ID node may be changed to one of the higher AlertLevels depending on whether the node needs to upload data (e.g., AlertLevel 3 status) or synchronize timer or other data with another node(e.g., Synchronize status). With this change in status flag, and the IDnode in state 815 broadcasting, the ID node awaits to receive a requestfrom another node that has received the broadcast and requested moreinformation via a SCAN_REQ message (factor 820) sent to the ID node fromthat other node. Once a SCAN_REQ message has been received by the IDnode (factor 820), the ID node that went into the alert mode because ithad not connected with another node within the alert interval canconnect with that other node, upload or share data as needed, and thenshift back to state 805 and restart the alert interval andnon-connectable intervals.

Master Node to ID Node Association Example

Advertising (broadcasting) and scanning (listening) are ways nodes maycommunicate during association operations. FIGS. 9-12 provide examplesof how network elements of a wireless node network (e.g., ID nodes,master nodes, and a server) may communicate and operate when connectingand associating as part of several exemplary wireless node networkoperations.

FIG. 9 is a diagram illustrating exemplary components of a wireless nodenetwork during an exemplary master-to-ID node association in accordancewith an embodiment. Referring now to FIG. 9, exemplary master node M1910 a is illustrated within communication range of exemplary ID node A920 a. Master node M1 910 a also has a communication path back to server900. As shown, master node M1 910 a is in a scanning or listening mode(e.g., indicated by the “M1 _(scan)” label) while ID node A 920 a is inan advertising or broadcasting mode (e.g., indicated by the “A_(adv)”label). In this example, M1 master node 910 a has captured the addressof ID node A 920 a through A's advertising of at least one advertisingdata packet, and has reported it to the server 900. In this manner, thecapturing and reporting operations effectively create a “passive”association between the nodes and proximity-based custodial control.Such an association may be recorded in the server, such as server 900,as part of association data, such as association data 540.

In another embodiment, passive association between a master node and IDnode may be extended to an “active” association or connection. Forexample, with reference to the embodiment shown in FIG. 9, server 900may instruct master node M1 910 a to associate, connect, or otherwisepair with ID node A 920 a, and forwards the required securityinformation (e.g., PIN credentials, security certificates, keys) tomaster node M1 910 a. Depending on the advertising state of ID node A920 a, ID node A 910 a may only be visible (discoverable) but notconnectable. In such a situation, the master node M1 910 a must waituntil ID node A 920 a is in a connectable state (e.g., the ID NodeGeneral Advertising state) and can be paired. As discussed above withreference to FIG. 8, each ID node has a certain time window during eachtime period where it can be paired or connected.

In this example, when the ID node A 920 a is successfully paired withmaster node M1 910 a, ID node A 920 a may no longer advertise itsaddress. By default, only an unassociated device will advertise itsaddress. A paired or associated node will only advertise its address ifinstructed to do so.

ID Node to ID Node Association Example

In various embodiments, an ID node may associate with or connect toother ID nodes. FIG. 10 is a diagram illustrating exemplary componentsof a wireless node network during an exemplary ID-to-ID node associationin accordance with an embodiment of the invention. Referring now to FIG.10, exemplary master node M1 910 a, ID node A 920 a, and server 900 aresimilarly disposed as shown in FIG. 9, but with the addition of ID nodeB 920 b, which is within communication range of ID node A 920 a. In thisexample, ID node A 920 a is running in query (scan) mode (e.g.,A_(scan)) listening for ID node B 920 b. When ID node A 910 a detects IDnode B 920 b advertising (e.g., B_(adv)) with one or more advertisingdata packets as part of an advertised message from ID node B 920 b, IDnode A 920 a identifies a status flag from the message indicating IDnode B 920 b has, for example, data (e.g., sensor data 350) for upload.As a result, ID node A 920 a logs the scan result (e.g., as a type ofassociation data 340) and, when next connected to master node M1 910 a,ID node A 920 a uploads the captured scan log information to the server900. In this manner, the ID node scanning, capturing, and reportingoperations effectively create a “passive” association between thedifferent ID nodes. Such a passive association may be recorded in theserver 900 as part of association data 540.

In another embodiment, passive association between two ID nodes may beextended to an “active” association or connection. For example, withreference to the embodiment shown in FIG. 10, based upon the capturedstatus flag and uploaded information about ID node B 920 b under thatmode, the server 900 may issue a request to ID node A 920 a throughmaster node M1 910 a to actively connect or pair with ID node B 920 bfor the purpose of downloading information from ID node B 920 b. In oneexample, security credentials that authorize the active connectionbetween ID node A 920 a and ID node B 920 b are downloaded to ID node A920 a from master node M1 910 a, which received them from server 900. Inanother example, the requisite security credentials may have beenpre-staged at ID node A 920 a. And rather than rely upon an ID node toID node connection, master node M1 may have connected directly with IDnode B 920 b if M1 was within communication range of ID node B 920 b.

Information Query ID Node to Master Node Example

An exemplary ID Node may also issue queries to other nodes, both masternodes and ID nodes. FIG. 11 is a diagram illustrating exemplarycomponents of a wireless node network during an exemplary ID-to-masternode query in accordance with an embodiment of the invention. Referringnow to FIG. 11, a similar group of nodes as shown in FIG. 9 appears,except that exemplary master node M1 910 a is in an advertising orbroadcasting mode (e.g., M1 _(adv)) while ID node A 920 a is in ascanning mode (e.g., A_(scan)). In this configuration, ID node A 920 amay query master node M1 910 a for information. In one embodiment, thequery may be initiated through the ID node setting its status flag. Therequested information may be information to be shared, such as a currenttime, location, or environmental information held by the master node M1910 a.

In a passive association example, ID node A 920 a in A_(scan) mode mayhave captured the address of master node M1 910 a. However, since an IDnode cannot directly connect to the server 900 to request pairingsecurity credentials (e.g., security pin information that authorizes anactive connection between ID node A 920 a and master node M1 910 a), apassive association and corresponding pairing will have been initiatedfrom the master node. In another example, it may be possible for ID nodeA 920 a to have the pairing credentials stored as security data 335 froma previous connection. This would allow ID node A 920 a then to initiatethe active association with master node M1 910 a after a passiveassociation.

Alert Level Advertising Example

As previously noted, a node may enter an alert stage or level in one ormore embodiments. For example, if a node has not received anacknowledgement from a master node for an advertising packet within aset period (e.g., an Alert Interval as described in some embodiments),the node will enter a particular alert stage for more specializedadvertising so that it may be “found” or pass along information. FIG. 12is a diagram illustrating exemplary components of a wireless nodenetwork during an exemplary alert advertising mode in accordance with anembodiment of the invention. Referring now to FIG. 12, a similar groupof nodes as shown in FIG. 9 appears, with the addition of another masternode (master node M2 910 b) and another ID node (ID node B 920 b).Exemplary ID node A 920 a is in an advertising or broadcasting mode(e.g., A_(adv)) while nodes M1, M2, and B are each in scanning mode(e.g., M1 _(scan), M2 _(scan), and B_(scan)). In this example andconfiguration as shown in FIG. 12, the status flag in an advertisingmessage from ID node A 920 a has been set to a particular alert level(e.g., Alert Level 2) in the header of the message, requesting anynearby master node to acknowledge it. In one example, this mode may beentered if ID node A 920 a has not connected with another node for a setperiod or time. In another example, ID node A 920 a may enter thisspecialized advertising mode upon received instructions (e.g., fromserver 900 or another nearby node) or a triggered condition (other thantime), such as when a sensor input (such as light) is detected orotherwise registered and the node issues continuous updates of itsaddress as a security feature. The ID node A 920 a set at this alertlevel and in this specialized advertising mode is thus set in an activepairing mode, waiting for pairing credentials.

From a passive association perspective, any node in scanning mode canpassively associate with such an advertising node (e.g., ID node A 920 ain this alert mode). Thus, in an embodiment, the Alert Level 2 statusflag in the advertising header broadcast by ID node A 920 a indicatesthat urgent and active intervention is requested, rather than merelypassively associate without an active connection.

From an active association perspective, any node that uploads thespecial advertising header of ID node A 920 a may be forwarded thesecurity credentials from the server 900. This would allow for the nodereceiving such credentials to actively associate or pair with ID node A920 a.

While FIG. 8 provides examples of how a node may advertise, and FIGS.9-12 provide examples of how different exemplary devices (e.g., IDnodes, master nodes, and a server) may advertise and associate indifferent ways, FIGS. 22A-C provide a progressive set of illustrationsthat expand upon how associating and disassociating may be appliedwithin an exemplary wireless node network. More specifically, FIGS.22A-C show how associations and disassociations may occur when anexemplary ID node is tracked and managed by a server and differentmaster nodes as the ID node moves through an exemplary transit path inaccordance with an exemplary embodiment of the invention.

Referring now to FIG. 22A, a structure 2200 is shown having an entry andexit point. In one example, the structure 2200 may be a corridor oranother part of a building or facility. In another example, structure2200 may be a conveyor system that transports an item and its ID nodefrom the entry point to the exit point. Master node M1 2210 a is locatednear the entry point of structure 2200 while master node M2 2210 b islocated near the exit point. Those skilled in the art will appreciatethat other master nodes may be disposed at additional points instructure 2200, but are not shown for sake of convenience and tosimplify the association hand-off explanation that follows. Server 100is operatively connected to each of master node M1 2210 a and masternode M2 2210 b via network 105.

In one embodiment, server 100 has access to context data 560 related tothe structure 2200, such as layout data 585 on dimensions and materialsmaking up structure 2200. Context data 560 may include historic data 575on how an ID node has operated and successfully been tracked as ittraverses structure 2200 from the entry point to the exist point. Forexample, server 100 may have context data indicating structure 2200 is aconveyor that can transport an item and its ID node from the entry pointto the exit point over a distance of 800 feet. The context data mayfurther indicate typical items are moved at a certain speed on theconveyor of structure 2200 and a nominal time from the entry point tothe exit point may be about 5 minutes. Thus, the server 100 has accessto context data about the environment within with an ID node isoperating and may leverage this to better and more accurately manage theID node.

In FIG. 22A, ID node A 2220 a is shown entering the structure 2200 atthe entry point. Here, ID node A 2220 a may be advertising in hopes ofconnecting with a master node as it enters structure 2200 with, forexample, a non-connectable interval of 10 seconds with a connectableinterval of 5 seconds. In this example, the server 100 knows that IDnode A 2220 a is located near the entry point and anticipates that IDnode A 2220 a should be coming near to master node M1 2210 a at theentry point. Thus, server 100 may set the connectable andnon-connectable intervals accordingly so as to provide a sufficientopportunity for ID node A 2220 a to connect to the next master nodealong the predicted path of the ID node and in accordance with the speedof travel.

Additionally, server 100 may set the alert interval to 1 minute in thiscontext. Here, if ID node A 2220 a is not connected to another nodewithin 1 minute, ID node A 2220 a may broadcast or advertise with amessage having a changed status flag that indicates an alert status sothat ID node A 2220 a can connect to a broader range of other nodes thatsee it is urgent for ID node A 2220 a to connect and, essentially, befound. Depending on the context (e.g., the type of conveyor, the speedof the conveyor, the density of nodes near the entry point, etc.), thoseskilled in the art will appreciate that the server 100 can adjust theadvertising cycle intervals to better accommodate the ID node's currentenvironment.

When master node M1 2210 a is scanning (listening), it may initiallydetect an advertising packet from ID node A 2220 a during node A'snon-connectable interval. But when ID node A 2220 a changes advertisingstates and broadcasts as a connectable node in the general advertisingstate (i.e., during the connectable interval), master node M1 2210 a mayrespond with a SCAN_REQ that acknowledge receipt of the broadcastedmessage and asks for further information from ID node A 2220 a. Masternode M1 2210 a receives the requested information from ID node A 2220 a,and then communicates with the server 100 to notify the server of itspassive association with ID node A 2220 a. Server 100 determines ifactive association is desired, and may authorize the active associationbetween master node M1 2210 a and ID node A 2220 a by sending securitycredentials to master node M1 2210 a, which allow the nodes to securelyconnect and share information. And master node M1 2210 a may determinethe location of ID node A 2220 a (or server 100 may do so by directingmaster node M1 and/or ID node A), and provide the location of ID node A2220 a to server 100. Thus, server 100 is able to manage and track thelocation of ID node A 2220 a as it enters structure 2220 via at leastassociation.

In FIG. 22B, ID node A 2220 a has traversed down part of the transitpath through structure 2200 while remaining associated with master nodeM1 2210 a. However, at some point master node M1 2210 a and ID node A2220 a are disassociated at the direction of server 100 (or when theycan no longer communicate). In one example where ID node A 2220 a is onthe conveyor within structure 2200, server 100 may instruct ID node A2220 a to go to a low power mode for a particular period of time inorder to, for example, conserve ID node power. In another example, thelow power mode may also provide better location accuracy. As the server100 has access to the context data, the server 100 may know that ID nodeA 2220 a was associated with master node M1 2210 a near the entry pointat a given time, and determine that ID node A 2220 a will not be nearthe exit point until the end of the particular period of time. With theID node A 2220 a programmed this way, once the particular periodelapses, the ID node A 2220 a should be near the exit point and mayagain be placed into a normal operation mode so that it can seek toconnect with master node M2 2210 b.

Similar to the association process discussed with respect to ID node Aand master node M1, ID node A 2220 a and master node M2 2210 b may beassociated as ID node A 2220 a approaches master node M2 2210 b near theexit point. Once connected, the node locations and association data areupdated on the server 100. And as ID node A 2220 a continues to movethrough structure 2200, ID node A 2200 a may arrive at the exit point asshown in FIG. 22C, where the node locations and association data areupdated once again on the server 100.

Those skilled in the art will appreciate how such principles may beapplied to further movements of an ID node as it is handed off (e.g.,via active/passive associations and disassociations) between othermaster nodes and keeping track of these associations and node locationson the server 100. Additionally, as server 100 tracks and monitorsassociations, disassociations, and contextual environmental operations,server 100 essentially learns how to better use context informationbetter track nodes, manage power used by ID nodes, and enhance accuracyfor locations.

Those skilled in the art will also appreciate the general tradeoff witha level of RF power level and accuracy of location. If a node's RF powerlevel is set high, it may advertise and connect with other nodes alonger distance away. But at such a high power level setting, theability for the system to discriminate between and locate differentnodes may be a challenge.

Association Management within a Wireless Node Network

As explained above in general, management of nodes may rely uponassociations created and tracked between nodes (or between a node andanother entity, such as a person, object, facility, piece of equipment,and the like). In some embodiments, the association relied upon may bean active association where the server expressly authorizes an activeconnection between nodes. In other embodiments, the association reliedupon may be a passive association where the master node (a type ofmanaging node) is associated with the other node, but not activelyconnected to the other node. By virtue of the passive association, theserver may be able to keep track of and manage the other node withoutrequiring an active association. Thus, those skilled in the art willappreciate that in still other embodiments, associations relied upon bythe server for managing a wireless node network may include both activeand passive associations and may be generally authenticated or, morespecially, authorize a secure connection that has a degree of protectionfor the connection and communications using that connection.

FIGS. 23-25 provide flow diagrams of exemplary methods for associationmanagement of a wireless node network having at least a plurality ofnodes and a server in accordance with different embodiments of thepresent invention involving active and passive association examples.Those skilled in the art will appreciate that each of these exemplarymethods for association management of a wireless node network may beimplemented by instructions stored on a non-transitory computer-readablemedium, which when executed perform the steps of the respective methodsdescribed below (e.g., methods 2300, 2400, and 2500) and the describedvariations of those methods.

Referring now to FIG. 23, method 2300 begins by identifying a first nodeas a potential for actively associating with a second node at step 2305.In one example, identifying the nodes for association may involvereviewing a message sent by the first node to determine statusinformation related to the first node, and analyzing the statusinformation to determine whether the first node should be associatedwith the second node. In a further example, the status information maycomprise one of a plurality of different status levels indicatingwhether the first node is requesting a connection to the second nodewhen at that particular status level.

Next, an association request is transmitted to the server in step 2310.In one example, the association request may identify the first node andsecond node to be associated and may request transmission of one or moreappropriate security credentials (e.g., PIN credentials, securitycertificates, keys, and the like) that may be used by the nodes toenable the first and second node to securely connect and share data aspart of associating. An embodiment may request only one credential as anauthorization credential from the server. Other embodiments may use twocredentials where one may be later uses as a credential with which toreply to challenges. For example, if an ID node is challenged, the IDnode may send a reply authorization credential so that the master nodecan confirm the response and supply the ID node with the appropriatesecurity credential for the authorized association. In some cases, an IDnode may have been supplied with such a reply authorization credential(also generally referred to as a key) by the server.

At step 2315, the second node receives a permissive response from theserver related to the association request. In an example, the permissiveresponse may include receiving a first authorization credential and asecond authorization credential from the server (which may be stored onthe nodes). As such, the first authorization credential and the secondauthorization credential may be created by the server as a type ofsecurity data, and may be provided to authorize connecting the firstnode and the second node and securely sharing information between thefirst node and the second node.

With this authorization from the server, the first node and second nodemay be associated at step 2320. In one example, the method 2300 mayassociate the nodes by establishing an authorized connection from thesecond node to the first node based upon the authorization credential.And the method 2300 may securely provide shared data between the firstnode and the second node according to a profile established by theserver after the first and second nodes are associated.

In an embodiment, the method 2300 may also comprise having the secondnode gaining responsibility for a task after the second node isassociated with the first node when responsibility for the task waspreviously with the first node. For example, when the second node ispowered by an external power source and the first node is powered by abattery, this may advantageously shift the responsibility to a node thatis better suited to perform the task (e.g., has more power available orhas a power source that does not need recharging or replacing).

FIG. 24 is a flow diagram illustrating another example method forassociation management of a wireless node network in accordance with anembodiment of the invention from the perspective of the server.Referring now to FIG. 24, method 2400 begins with the server receivingan association request sent from a second of the nodes at step 2405. Theassociation request asks for permission to associate a first of thenodes to the second node.

At step 2410, the server determines a location (actual or relative) ofthe first node and second node. In one embodiment, the server mayreceive location data for the second node. For example, when the secondnode is a master node, the location data for the second node may be GPScoordinates for the current location of the master node, which providesthis to the server. And in an embodiment, the server may determine alocation of the first node using at least one of a plurality of locationmethods available to the server for locating the first node, such asthose discussed in detail above (or a combination of such methods sothat a more refined location of the first node is determined).

At step 2415, the server determines if associating the first node to thesecond node is desired based at least upon the location of the firstnode and the location of the second node. In one embodiment, it may bedetermined if associating is desired by determining if associating thefirst node to the second node is anticipated based upon context data. Inanother embodiment, it may be determined if associating is desired byidentifying a current mode of filtering that limits potential nodes tobe associated, and granting the permission to associate the first nodeto the second node only if the current mode of filtering allows thefirst node to be associated with the second node. For example, this mayinvolve granting the permission only if the current mode of filteringdefines that the second node is within a locational range of the firstnode consistent with the current mode of filtering. This may be definedby a particular filtering mode, such as a local, regional, or globalfiltering mode that operates to restrict nodes that may associate withother nodes. As such, the method may alter the current mode of filteringto another mode of filtering that allows the first node to be associatedwith the second node as a sort of override of the current filtering mode(e.g., depending upon an alert status of the first node).

At step 2420, the server records new association data if it is desiredto associate the first node with the second node at step 2420. At step2425, the server transmits a response to the second node granting thepermission to associate the first node to the second node. In anembodiment, the server may first generate an authorization credentialthat authorizes connecting the first node and the second node andsharing information between the first node and the second node. This maybe by looking up the credential information or by going through aprocess to create specific an authorization credential that allows thetwo nodes to actively pair and share data. With the authorizationcredential, the server may transmit them as the response.

In another example, the server may have pre-staged an authorizationcredential related to the second node and a third node if the serveranticipates the second node will disassociate with the first node andlater request to associate with the third node. For example, this may bedone if the context indicates the second node (e.g., a master node) maybe placed in a container and need to connect with the third node in thefuture when the second node may lose its connection to the server.

Method 2400 may also include the server receiving shared data from thesecond node. The shared data may originate from the first node or mayhave parts that originate from both the first and second nodes. Forexample, the second node may have received the permission to associate,and actively paired with the first node in a secure manner. The firstnode may have indicated it has data to upload (e.g., sensor data), andthe second node may receive the data from the first node. Subsequent tothat sharing, the second node may upload the shared sensor data from thefirst node by transmitting it to the server.

The method may further comprise instructing the second node to take overresponsibility for a task previously performed by the first node afterthe second node is associated with the first node. For example, when thesecond node is powered by an external power source and the first node ispowered by a battery, the responsibility for certain tasks may be takenover by the node with a more robust power supply (e.g., the node poweredby an external power source).

In more detail, the responsibility for certain tasks may be established,tracked and changed with a programmable profile. For example, in oneembodiment, the server may establish a profile for how long the taskresponsibility would change. In some cases, the profile may define aperiod of time for how long a node having this profile would haveresponsibility for a certain task before it would revert back to adefault node. In another example, a node (such as a master node) mayhave a default condition trigger (like a low power situation or when itcannot communicate with the server) that can override such a profile sothat it does not take on more responsibilities under particularconditions.

Furthermore, an embodiment may have the master node deciding what othernode may take on responsibility for certain tasks. This may be helpfulin situations where access to the server may be limited (e.g., anairborne environment). However, managing such a profile may be moreeasily accomplished in other embodiments with easier access to moretypes of context data on the server level.

In an embodiment that implements association management as a system,such an exemplary system for association management of a wireless nodenetwork may comprise a first node, a second node, and a server. Thesecond node includes a node processing unit, a node volatile memorycoupled to the node processing unit, a first communication interfacecoupled to the node processing unit, and a second communicationinterface coupled to the node processing unit. The first communicationinterface provides a short-range communication path between the firstnode and the second node and the second communication interface providesa longer range communication path between the second node and theserver.

The server includes a server processing unit, a server volatile memorycoupled to the processing unit, and a third communication interface thatprovides a longer range communication path between the server and thesecond communication interface of the second node.

The node volatile memory maintains at least a first program code section(e.g., master control and management code 425 or parts thereof) whilethe server volatile memory maintains at least a second program codesection (e.g., server control and management code 525 or parts thereof).

When executing the first program code section resident in the nodevolatile memory, the node processing unit of the second node isoperative to identify the first node as a potential for associating withthe second node, transmit an association request over the secondcommunication interface to the server, receive an association response(having at least authorization information generated by the server) overthe second communication interface from the server, provide theauthorization information to the first node, and associate the firstnode and the second node.

In one example, the node processing unit may be further operative toreview status information related to the first node to determine whetherthe first node desires association with the second node. In anotherexample, the node processing unit may be further operative to securelyprovide shared data between the first and second node after the firstand second node are associated and in accordance with a sharing profileprovided by the server. The sharing profile may define types ofinformation to be securely shared between particular nodes.

When executing the second program code section resident in the servervolatile memory, the server processing unit is operative to determine alocation of the first node and second node, determine if associating thefirst node to the second node is desired based at least upon thelocation of the first node and the location of the second node, storenew association data in the server volatile memory if it is desired toassociate the first node with the second node, and transmit theauthorization response to the second node granting the permission toassociate the first node to the second node.

In one embodiment, the second node in the system may take overresponsibility of a task previously handled by the first node after thesecond node is successfully associated with the first node. For example,when the second node is powered by an external power source and thefirst node is powered by a battery, the system may be more effectivelyand efficiently managed by reassigning a task (especially a task thatinvolves a significant expenditure of power, a series of operations overa significant period of time, or both) to another node, such as thesecond node, which has more power available than the first node.

In another embodiment, the server processing unit may be furtheroperative to set a current mode of filtering that limits potential nodesto be associated, and grant the permission to associate the first nodeto the second node only if the current mode of filtering allows thefirst node to be associated with the second node. In a furtherembodiment, the server processing unit may be further operative to alter(e.g., override) the current mode of filtering to a different mode offiltering. In this way, the server may adapt how nodes are managed andallow the first node to be associated with the second node if it isdesired, such as then the first node is in an alert status level andurgently is requesting connection to a larger group of nodes thanpermitted under the current mode of filtering.

While the exemplary methods illustrated in FIGS. 23 and 24 focus onactive associations, FIG. 25 is a flow diagram illustrating an examplemethod for association management of a wireless node network having atleast a plurality of nodes and a server in accordance with anembodiment, but from the perspective of a node that is to be passivelyassociated with another node. Referring now to FIG. 25, method 2500begins with a second of the nodes receiving a message broadcasted from afirst of the nodes at step 2505. At step 2510, the second node capturesan address of the first node from the message. At step 2515, the firstnode and the second node are associated by storing the captured addressof the first node and an address of the second node as association datain a memory of the second node. At step 2520, the second node transmitsthe association data to the server.

At some point, the server may be updated by the second node with updatedassociation data when the second node does not receive an additionalmessage broadcast from the first node. For example, the second node andthe first node may stay associated and securely connected for a periodof time, but eventually the first node may move such that the connectionis no longer viable or the first node may move closer to another nodealong the anticipated path it is traveling (e.g., an anticipatedshipping path along a conveyor within a structure from an entry point ofthe structure but now closer to an exit point of the structure). As thefirst node travels on the conveyor, it may get closer to another nodenear the exit point and is better managed by an association with thatother node near the exit point. Thus, the updated association datareflects that the first node is disassociated from the second node.

Method 2500 may further include having the second node determining alocation of the first node, and updating the server with a currentlocation of the second node and the determined location of the firstnode. Additionally, method 2500 may include receiving locationinformation from the server that defines a refined location of the firstnode.

In an embodiment that implements passive association management as amanaging node (e.g., a master node) in a wireless node having at leastanother node and a server, such an exemplary managing node comprises aprocessing unit, a first and second communication interface each coupledto the processing unit, a volatile memory coupled to the processingunit, and a memory storage coupled to the processing unit. The firstcommunication interface provides a first communication path to the othernode, can receive a message broadcast from the other node, and providethe message to the processing unit. The second communication interfaceproviding a second communication path to the server.

The memory storage may maintain at least a node association managermodule as program code to be executed by the processing unit. When theprocessing unit loads the module into volatile memory and executesinstructions of the module, the processing unit is operative to receivethe message from the first communication interface, capture an addressof the another node from the message, store the captured address of theanother node and an address of the managing node as part of associationdata in the memory storage, and transmit the association data to theserver through the second communication interface.

In one example, the memory storage also maintains a location managermodule and, when the processing unit also loads the location managermodule into volatile memory and executes instructions of that module,the processing unit is operative to determine a location of the othernode, determine a current location of the managing node (e.g., via GPSlocation signals), and update the server with the current location ofthe managing node and the determined location of the other node.

The managing node may be further operative to update the server withupdated association data when the first communication interface does notreceive an additional message broadcast from the other node. The updatedassociation data may reflect that the other node is disassociated fromthe managing node.

Context Management within a Wireless Node Network

As explained above in general, management of nodes may rely upon thecontextual environment of the nodes. As shown in FIG. 5, server 100 hasaccess to a wide variety of different context data 560. Context data,such as data 560, may include a wide variety of data that generallyrelates to the environment in which the nodes are operating and may beused to advantageously provide enhanced node management capabilities inaccordance with embodiments of the present invention. As such, the useof such context data provides a data foundation in an embodiment so thatthe server may better and more efficiently implement management tasksrelated to nodes in the network, and adjust such tasks to account forrelevant context data as nodes move within the network (e.g., as an IDnode moves with an item being shipped along an anticipated or predictedtransit path from an origin to a destination). For example, the servertake advantage of its ability to rely upon relevant context data toadvantageously alter how it instructs a node operate, how it associatesa node with the another node, how it can better locate a node, and howit can more efficiently track and respond to requests to report thelocation of the node.

FIG. 26 is a flow diagram illustrating an exemplary method for contextmanagement of a wireless node network in accordance with an embodimentof the invention. Referring now to FIG. 26, method 2600 begins at step2605 by identifying, by the server, at least one of the nodes. In oneexample, such as that shown in FIG. 22a , server 100 may identify IDnode A 2220 a as part of communications received from master node M12210 a. At step 2610, the server determines context data that relates toan operating environment of the identified node as the identified nodemoves within the operating environment.

In one embodiment, the context data may include one or more types ofdata, such as scan data, historic data, shipment data, RF data, andlayout data. For the example shown in FIG. 22a , server 100 may accesscontext data 560 (which may be kept in context database 565) todetermine parts of the context data 560 that relate to the operatingenvironment of ID node A 2220 a. Such context data 560 may include, inthis example, shipment data that relates the item being shipped that isconnected to ID node A 2220 a, scan data for when the item connected toID node A 2220 a was scanned upon entering structure 2200, historic datafor how long it takes a node to traverse the conveyor located withinstructure 2200, and layout data on dimensions of structure 220. Thoseskilled in the art will appreciate that context data may includeoperational environment information created within the wireless nodenetwork or created by a third party (e.g., weather information relatedto the operating environment of ID node A 2220 a).

While the server determines context data that relates to an operatingenvironment of the identified node in one embodiment, such a current oranticipated operating environment for a node in a more detailedembodiment may include one or more types of environments. For example,the current or anticipated operating environment for a node may includean electronic communication environment, a physical environment of ananticipated path along with a node moves, a conveyance environmentrelated to how a node moves, and a density environment related to thedensity of nodes within an area near a particular node identified by theserver.

Back at step 2610, the determining step may involve determining thecontext data that relates to an anticipated operating environment of theidentified node as the identified node moves in a predicted path towardsa location of another node. In another example, the determining step mayinvolve determining the context data that relates to the anticipatedoperating environment of the identified node and an anticipatedoperating environment of the another node as the identified node movesin the predicted path towards the another node for an expectedassociation with the another node

At step 2615, the server performs a management task related to theidentified node with an adjustment made to account for the determinedcontext data. When the determined context data (such as RF signaldegradation information) indicates that no adjustment is actually neededwhen performing the task, no adjustment is made given the determinedcontext data. Thus, those skilled in the art will appreciate that anadjustment may be made when needed contextually and is not required atall times.

In one embodiment, performing the management task may comprise generallyinstructing the identified node to alter its operation based upon thedetermined context data. For example, server 100 may perform themanagement task of instructing ID node A 2220 a to change itsconnectable and non-connectable intervals as it approaches master nodeM1 (which server 100 knows from context data, such as scan datagenerated when node A entered structure 2200). Thus, in this example,server 100 is able to leverage enhanced visibility of ID node A 2220 abased upon context data and advantageously alter the operation of node Ato increase the node's chance of successfully associating with masternode M1 2210 a.

In other embodiment, performing the management task may compriseassociating the identified node with another node with the adjustmentmade to alter an associating parameter based upon the determined contextdata. In other words, context data may be helpful as part of associatingnodes. In one example, the associating parameter may include at leastone altered timing interval related to associating the identified nodewith the other node, such as an alert interval or connectable interval.These intervals are parameters that may be altered as part ofadjustments made when a server associates two nodes and, for example,sets the intervals to more appropriate time durations in order toenhance the chance and opportunity the nodes have to actively pair andsecurely share data as needed.

In yet another embodiment, performing the management task may compriselocating the identified node with an adjustment made to a power settingbased upon the determined context data. In one example, the powersetting adjustment is done to a master node in direct communication withthe server. In another example, the power setting adjustment may be doneto an ID node, which is passed this operational adjustment informationfrom another node. In one embodiment, the power setting itself maycomprise an output power level adjusted to account for an adversecondition in the operating environment of the identified node (e.g., amaster node with an adjusted RF output signal level). The adversecondition may be, for example, an adverse RF communication environmentwhere structure attenuates or otherwise impedes normal RFcommunications. In another example, the adverse condition may be ahighly dense population of nodes close to the identified node.

In more detail, the output power level may be adjusted to account for ashielding condition in the operating environment of the first node. Sucha shielding condition may be caused, for example, by one or more ofpackaging, package contents, proximate package, proximate packagecontents, and physical infrastructure in the operating environment ofthe first node. For example, if the identified node is located near ametal container, it is operating in an adverse RF communicationsenvironment where it may have its output power level increased based onthis context data in order to better deal with the adverse shieldingcondition.

In still another embodiment, performing the management task may compriseproviding the location of the identified node in response to a requestreceived by the server related to a status of the identified node. Forexample, if server 100 receives a request from user access device 205about the status of ID node A 2220 a, server 100 is able to provide thelocation of node A as being within structure 2200, but refined as beingclose to the entry of the structure given the adjustment to account forcontextual data, such as scan data related to the item being shippedwith node A 2220 a.

Those skilled in the art will appreciate that method 2600 as disclosedand explained above in various embodiments may be implemented on aserver, such as server 100 illustrated in FIGS. 5 and 22A, running oneor more parts of server control and management code 525 (e.g., thecontext based node manager). Such code may be stored on a non-transitorycomputer-readable medium such as memory storage 515 on server 100. Thus,when executing code 525, the server's processing unit 500 may beoperative to perform operations or steps from the exemplary methodsdisclosed above, including method 2600 and variations of that method.

Node Location Determination Methodologies

As part of managing and operating a wireless node network in accordancewith one or more embodiments of the invention, such as tracking ID nodeA 2220 a in FIGS. 22A-C, determining a node's location is performed. Asexplained above, an exemplary ID node may be directly or indirectlydependent on a master node to determine its location. In the embodimentsdiscussed and described herein, a location of a node may generallyencompass a current or past location. For example, an embodiment thatdetermines a node's location may be a current location if the node isnot moving, but may necessarily determine the location as a pastlocation should the node be in a state of motion.

Likewise, the term location alone may include a position with varyingdegrees of precision. For example, a location may encompass an actualposition with defined coordinates in three-dimensional space, but use ofthe term location may also include merely a relative position. Thus, theterm location is intended to have a general meaning unless otherwiseexpressly limited to a more specific type of location.

Determining node location may done by a master node alone, the serveralone, or the master node working together with the server. And on suchdevices, embodiments may use one or more methodologies to determine anode's location and further refine the location. Such examplemethodologies may include, but are not limited to, determining nodelocation may relate to controlling an RF characteristic of a node (e.g.,an RF output signal level and/or RF receiver sensitivity level),determining relative proximity, considering association information,considering location adjustments for context information and an RFenvironment, chaining triangulation, as well as hierarchical andadaptive methods that combine various location methodologies. A moredetailed description of these exemplary node location determinationtechniques is provided below.

Location Through Proximity

In one embodiment, a signal strength measurement between two or morenodes may be used to determine the proximity of the nodes. If neithernode's actual location is known, one embodiment may infer a locationrelationship of the two nodes through proximity.

Proximity when Varying Power Characteristics

For example, an exemplary method of determining a node's location in awireless node network of nodes may involve varying a node's powercharacteristic, such as the output power of one of the nodes. Generallyand as explained with reference to FIG. 13, the power characteristic maybe varied to identify closer ones of the nodes to the node broadcasting.The node broadcasting may transmit one or a series of signals whileother nodes may report receiving one or more of the signals. Those othernodes that receive at least one signal broadcast from the transmittingnode may be deemed part of a close group of nodes. And as the powercharacteristic is varied (increased or decreased or both), a closestgroup of nodes (or single node) may be identified as the smallest groupof nodes of those that receive at least one signal from the broadcastingnode. Accordingly, while not absolute, a type of location for thebroadcasting node may be determined based on the closest one or group ofnodes. This may be repeated for neighboring nodes to yield a set ofclosest node information for each of the nodes. In more detail, anexemplary set of closest node information for each of the nodes mayinclude which nodes are closest (via the lowest power characteristic)and more robustly supplement this information with which other nodes areincrementally further away (via increasingly larger powercharacteristics). Thus, the set of closest node information provides thebasis for a determination of how close the nodes in the network are toeach other, which provides a type of location determination for eachnode.

Additionally, context data may be referenced in certain embodiments tofurther enhance determining how close the nodes are to each other. Forexample, combining the set of closest node information with contextdata, such as scan information that registers when an item changescustodial control in a delivery system, may further refine how todetermine the location of the nodes. Scan and other context informationwill help determine if one or more of the nodes, for example, are knownto be in the same container, vehicle or moving on a belt together. Thus,this type of context data may be integrated into a further step ofrefining how close the nodes are to each other based upon the contextdata.

In general, a location of a node based upon proximity may be determinedwhen a power characteristic of nodes is changed or varied in a wirelessnode network. FIG. 28 is a flow diagram illustrating an exemplary methodfor location determination by varying a power characteristic of nodes ina wireless node network in accordance with an embodiment of theinvention. Referring now to FIG. 28, method 2800 begins by at step 2805by instructing a first of the nodes to vary the power characteristic forone or more signals broadcast by the first node. In a more detailedembodiment, such an instruction may cause the first node, for example,to incrementally decrease or incrementally increase the powercharacteristic (such as an output power level) between values.

At step 2810, method 2800 continues by identifying a first group ofother nodes in the wireless node network that are near the first nodebased upon those of the other nodes that received at least one of thesignals broadcast by the first node as the first node varies the powercharacteristic. In a further embodiment, step 2810 may incrementallyidentifying which of the first group of other nodes are receiving atleast one of the broadcast signals as the first node incrementallyvaries the output power level of the signals broadcast. Theincrementally identified nodes may be deemed a set of increasingly closenodes to the first node.

At step 2815, method 2800 continues by identifying a closest one or moreof the other nodes as a smallest group of the other nodes that receivedat least one of the one or more signals broadcast by the first node asthe first node varies the power characteristic.

At step 2820, method 2800 concludes by determining a location of thefirst node based upon the closest one or more of the other nodes. Thus,as the power characteristic is varied, the group of nodes that havereceived at least one of the signals broadcast by the first node maychange and the smallest such group being a closest group of nodes (evenif just one node) to the first node. In a more detailed embodiment, step2820 may comprise determining the location of the first node based uponthe closest one or more of the other nodes and the set of increasinglyclose nodes to the first node as the set of increasingly close nodesprovides more detailed proximity information for a refined locationdetermination.

For example, referring to FIG. 14, the set of increasingly close nodesto the ID node F 920 f may include node M3 as being farthest away and M1being closer than M3. When the power characteristic of ID node Fincrementally decreases, and its output power level changes from P1 toP2, M3 can no longer receive the signal, but M1 and M2 still do. And asthe power characteristic of ID node F continues to incrementallydecrease, and its output power level is changed from P2 to P3, M1 can nolonger receive the signal, but only M2 does as the last of the nodesclosest to ID node F. Thus, in this example, determining the location ofID node F may be based upon the fact that M2 is the closest node and theset of increasingly close nodes include M1 and M3 with M1 being closerthan M3.

In another embodiment, one or more further refinements to the firstnodes location may be performed. In one example, steps 2805-2820 may berepeated where a second of the nodes is instructed to vary the powercharacteristic for one or more signals broadcast by the second node, andthen method 2800 may further refine the location of the first node basedupon a location of the second node. In a more detailed example, steps2805-2820 may be repeated where a second of the nodes is instructed tovary the power characteristic for one or more signals broadcast by thesecond node, and then method 2800 may further the location of the firstnode based upon a location of the second node and a set of increasinglyclose nodes to the second node. With this increasingly cross-relatedinformation on what nodes are closer to other nodes and to what degree,which may be further repeated for additional nodes, embodiments mayfurther refine the location of the first node within the network.

Method 2800 may further include determining context data related to thefirst node, and refining the location of the first node based upon thecontext data. In an embodiment where the power characteristic is outputpower level, the incremental changes in the output power level of thebroadcast signal in steps 2805-2815 may be set according to the contextdata.

Method 2800 may also determine the context data to be related to theclosest node to the first node, and refine the location of the firstnode based upon the context data. In still another example, method 2800may determine the context data to be related to the incrementallyidentified nodes in the set of increasingly close nodes to the firstnode, and refining the location of the first node based upon the contextdata. For example, the closest node and the set of increasingly closenodes may have scan data that indicate they are within the samecontainer. This exemplary context data may be used to further refine thelocation of the node being located, which may help efficiently determinethat node is near the container. As such, those skilled in the willappreciate that context data for the node being located as well as nodesidentified to be close to that node may provide relevant input toadvantageously help further refine the location of the node.

Those skilled in the art will appreciate that method 2800 as disclosedand explained above in various embodiments may be implemented on aserver apparatus, such as server 100 illustrated in FIGS. 5 and 22A,running one or more parts of server control and management code 525(e.g., the location manager). Such code may be stored on anon-transitory computer-readable medium such as memory storage 515 onserver 100. Thus, when executing code 525, the server's processing unit500 may be operative to perform operations or steps from the exemplarymethods disclosed above, including method 2800 and variations of thatmethod.

An embodiment of such a server apparatus may include a server (such asserver 100) operative to communicate with a plurality of nodes in thewireless node network. As explained with respect to FIG. 5, the servergenerally includes a server processing unit, a server volatile memory, aserver memory storage, and at least one communication interface. In thisembodiment, the volatile memory, memory storage, and communicationinterface are each coupled to the processing unit. The memory storagemaintains at least a program code section and location data related to alocation of one or more of the nodes. The communication interfaceprovides a communication path operatively coupling the server with thenodes.

The server processing unit, as mentioned above, is operative whenrunning the program code section, to perform the steps and operations asdescribed above relative to method 2800 and variations of that methoddescribed above.

Proximity when Observing Signal Patterns and Strengths Over a TimePeriod

In another embodiment, an improved method for determining a node'slocation through proximity may include analyzing the signal patterns andstrengths between an advertising node and a listening node. In oneembodiment, a threshold may be set for association based on an observedmessage count and/or recorded signal strength within a specific timeperiod may improve the ability to locate a node (e.g., an ID node) tothat of another node (e.g., a master node). In some embodiments, theobserved message count may be implemented as an averaged count over arepeated time periods. Further still, other embodiments may filteroutlying observations in the observation data set to help improve thequality of data relied upon for setting a threshold for association and,as a result, determine a node's location.

In a more detailed example, an improved method for determining a node'slocation through proximity may show captured advertising message countsas a component for a node's location and determining a node's directionof travel. In this example, two exemplary master nodes (e.g., masternode M1 910 a and M2 910 b) may capture advertising messages from one IDnode (e.g., ID node A 920 a). Master node M1 may observe and capture(e.g., record information related to the observation) 60 messages fromID node A within a 2 minute period, while master node M2 only observesand captures 7 advertising messages from ID node A within that sameperiod. Based upon the difference in how often messages are observedfrom ID node A by master node M1 compared to those observed by masternode M2, the system is able to determine that ID node A would moreproximate to master node M1, and it's known location.

In a further embodiment, comparing the average time stamp of thecaptured records may allow the system can make a more accuratedetermination of location. For example, if the average captured messagefound on master node M2 is increasingly growing larger (e.g., takinglonger for messages to go from ID node A to master node M2), thisindicates ID node A is moving away from master node M2. If the averagecaptured message found on master node M2 is growing increasingly largerwhile the average captured message found on master node M1 isincreasingly growing smaller, this indicates ID node A is moving awayfrom master node M2 and toward master node M1. Thus, over a number ofobserved time periods, the change in message timing (transmission toreception) may also be relied upon to enhance or refine a node'slocation.

In yet another embodiment, the observed signal strength may be acomponent in location determination and estimating direction of traveland may allow the system can make a more accurate determination oflocation. For example, two master nodes (M1 910 a and M2 920 b) may becapturing advertising messages from a node (ID node A 920 a). M1captures 60 messages from ID node A within 2 minutes, while M2 capturesonly 7 messages. The average signal strength observed for signals fromID node A by master node M1 is higher compared to the average signalstrength observed by master node M2. Based upon this observed signalstrength information, the system would determine that ID node A to be atM1, but a predicted path may indicate ID node A is heading towards M2.As the master nodes M1 and M2 continue to capture records, the system(e.g., management code 524 operating on server 900, which is incommunication with M1 and M2) processes the continued feed of capturerecords from M1 and M2. With this observed signal strength information,the server 900 would expect that the count and average signal strengthof messages from ID node A over the time period observed (2 minutes) toincrease for observations at M2 and to decrease for observations at M1when ID node A is physically moving closer to M2 and away from M1. Thus,the change in observed powers levels and in how often messages areobserved may indicate actual node movement in an embodiment.

Basing node proximity location and node directional determinations onobserved signal patterns and characteristic strengths over a period oftime has the advantage of reducing the likelihood of unwanted andspurious signal anomalies causing an ID node's location to beincorrectly determined. And the above exemplary methods for determiningmovement characteristics of a node (e.g., moving closer to one node,moving closer to one but away from another, etc.) as part of refiningthe node location may be applied in combination with the variousembodiments for determining node location described herein.

FIG. 27 is a flow diagram illustrating an exemplary method for proximitylocating a node in a wireless node network based upon observed signalpatterns and characteristic indications over a period of time inaccordance with an embodiment of the invention. Referring now to FIG.27, method 2700 begins at step 2705 by instructing a first and a secondother nodes to detect any message broadcast from the one node over aperiod of time. The period of time may be set based upon a variety offactors, such as context data. In more detail, the period of time may bedynamically changed based upon context data as the one node moves intodifferent contextual environments.

Method 2700 has the server receiving a first indication from the firstother node at step 2710 and receiving a second indication from thesecond other node at step 2715. Finally, the method 2700 determines alocation of the one node based upon a difference in the first indicationand the second indication at step 2720.

The first indication is related to a characteristic of messagesbroadcast from the one node that are detected by the first other nodeduring the period of time. Likewise, the second indication is related tothe characteristic of messages broadcast from the one node that aredetected by the second other node during the period of time. Theseindications may include, for example, a count of messages received bythe respective other nodes, a transit time factor (e.g., an averagetransit time for a message to be detected after broadcast), and anaverage signal strength.

In one embodiment, the first indication may be a first count of messagesbroadcast from the one node that are detected by the first other nodeduring the period of time, and the second indication may be a secondcount of messages broadcast from the one node that are detected by thesecond other node during the period of time. As such, determining thelocation of the one node may be the location that is closer to the firstother node than the second other node when the first count is greaterthan the second count. Additionally, the method 2700 may further includedetermining an actual node movement direction for the one node basedupon comparing the first count and the second count over a plurality oftime periods. For example, the method 2700 may repeat observations overseveral of these time periods and track the first count and second countover time to determine which is increasing, which is decreasing, anddetermine movement of the one node based upon these measurements overtime.

In another detailed embodiment, the first indication may be a first timefactor of messages broadcast from the one node that are detected by thefirst other node during the predetermined time period, and the secondindication may be a second time factor of messages broadcast from theone node that are detected by the second other node during the period oftime. And an actual node movement direction for the one node may bebased upon comparing the first time factor and the second time factor.In a more detailed embodiment, the first time factor may be an averagetransit time for a message detected at the first other node to go fromthe one node to the first other node, and the second time factor is anaverage transit time for a message detected at the second other node togo from the one node to the second other node. As such, determining thelocation of the one node may be that the location is closer to the firstother node than the second other node when the first time factor is lessthan the second time factor.

In yet another embodiment, the first indication may be a first averagesignal strength of messages broadcast from the one node that aredetected by the first other node during the period of time, and thesecond indication may be a second average signal strength of messagesbroadcast from the one node that are detected by the second other nodeduring the period of time. As such, determining the location of the onenode may be that the location is closer to the first other node than thesecond other node when the first average signal strength is greater thanthe second average signal strength.

The method 2700 may also include, in an embodiment, observing a degreeof change in the first average signal strength and a degree of change inthe second average signal strength over repeated time periods, anddetermining an actual node movement direction for the one node basedupon comparing the degree of change in the first average signal strengthand the degree of change in the second average signal strength.

In another embodiment, the method 2700 may also refine the determinedlocation of the one node. In this embodiment, the method 2700 mayfurther comprise refining the location of the one node based upon atleast one of a first updated location received from the first other nodeand a second updated location received from the second other node. Forexample, when first other node is a mobile master node and it is thecloser of the two nodes to the one node being located, the embodimentcan take advantage of the location signaling onboard the first othernode that provides the current location of the first other node. Thatcurrent location data may be transmitted by the first other node to theserver to update the server in its calculation of the location for theone node.

In still another embodiment, the method 2700 may layer context data withthe determined location to refine the location of the node. Context datarelated to the one node may be determined by the server, and so thelocation of the one node may be refined based upon that context data. Inanother example, context data related to the closer of the first othernode and the second other node when compared to the location of the onenode. For example, the server may be aware that a particular master nodeis closer to the one node compared to a second master node, and that theparticular master node is within a container. With this additionalcontext data related to the particular master node, the server mayrefine the location of the one node based upon the context data. Otherexemplary types of relevant context data may be relied upon whenrefining the location of the one node, such as context data of aparticular shielding associated with the environment near the particularmaster node (e.g., a particular type of ULD having known RF shieldingcharacteristics, etc.)

Additionally, the method 2700 may involve looking to see if the one nodeis behaving as expected. More specifically, a further embodiment of themethod 2700 may further compare the location of the one node to apredicted path of the one node to determine if the one node is locatedoutside the predicted path. This may allow the server to use learned,historic data when creating a predicted path, and keep track of the onenode relative to being within an acceptable range associated with thispredicted path. The method may also generate a notification if the onenode is outside the predicted path. In this manner, actionable tasks canthen be taken to locate the one node—e.g., changing filter mode optionsfor nodes in that general area, etc.

Those skilled in the art will appreciate that method 2700 as disclosedand explained above in various embodiments may be implemented on aserver, such as server 100 illustrated in FIGS. 5 and 22A, running oneor more parts of server control and management code 525 (e.g., thelocation manager). Such code may be stored on a non-transitorycomputer-readable medium such as memory storage 515 on server 100. Thus,when executing code 525, the server's processing unit 500 may beoperative to perform operations or steps from the exemplary methodsdisclosed above, including method 2700 and variations of that method.

Association Driven Locating with Variable RF Characteristics

As noted above, a signal strength measurement between two or more nodesmay be used to determine relative distance between nodes. If one of thenodes has a known location (such as master node M1 910 a), a relativelocation of one or more nodes within a range of the known location nodeis generally a function of how accurate the system may determine adistance between the node with known location and associated nodes. Inother words, an embodiment may identify a relative location of an itemand its related node by relying upon association-driven variablelow-power RF output signals to determine a distance the node is from aknown location.

Location Determination Through Master Node Advertise

As generally mentioned above, determining node location may relate tocontrolling an RF characteristic of a node (e.g., an RF output signallevel and/or RF receiver sensitivity level) and, more specifically, mayinvolve aspects of controlling master node advertising. FIG. 13 is adiagram illustrating an exemplary location determination using masternode advertise in accordance with an embodiment of the invention. In theillustrated embodiment shown in FIG. 13, a master node, such as masternode M1 910 a, with a known location is broadcasting an advertisingmessage at varying RF output power levels. FIG. 13 illustrates theexemplary different RF output power levels as concentric ranges1305-1315 about master node M1 910 a. Thus, master node M1 910 a maybroadcast at a maximum power P1, related to range 1305, but may controlthe RF output power level and dynamically change the RF output powerlevel to P2 and broadcast at a smaller range 1310, or to P3 andbroadcast to an even smaller range 1315.

In the illustrated embodiment, receiving ID nodes A-E 920 a-920 e are inquery (scan) mode and can each use the received signal at differentlevels to determine how far away from the transmitting M1 they arelocated. Those skilled in the art will appreciate that while theillustrated embodiment shown in FIG. 13 has the receiving nodes all asID nodes, other embodiments may have receiving nodes be either master orID nodes or a mixture.

In the exemplary embodiment of FIG. 13, the location for nodes A-E maybe determined based upon the known location of master node M1 910 a.That location, plus a range measurement when each of respectivereceiving nodes A-E last receives a signal from node M1, and factoringin a confidence factor of the range measurement, provides a locationdetermination for the nodes according to variable RF signal power.Depending on a quality of the range measurement, the individualreceiving nodes may or may not have an individually calculated location.In yet another embodiment, if third party or context data, such as scaninformation, is available, a refined location may be determined usingsuch data as an additional confidence factor. As the communication rangeof M1 is limited from P1 to P3, the accuracy of location by associationgoes up.

In the illustrated example of FIG. 13, an exemplary method ofdetermining a node's location may be described that uses master nodeadvertising. First, when the master node M1's variable power short rangecommunication interface 480 is set to P1, its maximum output, masternode M1 910 a is seen by each of ID nodes A-E 920 a-920 e. Based uponanalytics or historic measurements, the open air performance (optimalrange) of the radio in M1's variable power short range communicationinterface 480 at P1 power level may have been previously been found tobe approximately 30 feet. Thus, without the need to examine RSSI levelsfrom the individual ID nodes A-E 920 a-920 e and without the need foractive calibration phases, the system may know that ID nodes A-E arewithin 30 feet of master node M1 910 a.

Next, when the master node M1's variable power short range communicationinterface 480 is set to P2, a medium output level in this example,master node M1 is seen by nodes A and B. From previous analytics orhistoric measurements, it was determined the open air performance(optimal range) of the master node M1's variable power short rangecommunication interface 480 running at P2 power level is approximately15 feet. Thus, without the need to examine RSSI levels from theindividual nodes, we know ID nodes A 920 a and B 920 b are within 15feet of master node M1. Furthermore, we know the ID nodes no longerreceiving the broadcasted RF signal from master node M1 910 a (e.g., IDnodes C 920 c, D 920 d, and E 920 e) are somewhere within 30 feet ofmaster node M1 910 a, but probably more than 15 feet away from M1.

And when the master node M1's variable power short range communicationinterface 480 is set to P3, its minimum output level in this example, itis seen by ID node B 920 b. From previous analytics or historicmeasurements, it was determined the open air performance (optimal range)of the master node M1's variable power short range communicationinterface 480 running at P3 power level is approximately 5 feet. Thus,without the need to examine RSSI levels from the individual ID nodes, weknow the location of ID node B 920 b is within 5 feet of the knownlocation of master node M1 910 a.

The ranging steps, as discussed in the example above, may then berepeated for any of the identified nodes in order to build a moreaccurate picture of the relative location of each node. The granularityof RF characteristic settings (e.g., the RF output signal power levelsetting) will provide more granularity of location differentiation whenperforming the ranging steps. In one embodiment, the ranging steps maybe performed over a set of gross RF characteristics settings (e.g., fewsettings over a wide range), and similar steps may then be performedover more select ranges for the RF characteristics settings.

FIG. 29 is a flow diagram illustrating an exemplary method for locationdetermination using one or more associations of nodes in a wireless nodenetwork in accordance with an embodiment of the invention. Referring nowto FIG. 29, method 2900 begins at step 2905 where a first of the nodesbroadcasts one or more first messages at a first anticipated orpredicted range distance. In one embodiment, the first anticipated rangedistance is an optimal range for the first node. For example, the firstnode's radio in its communication interface may have a maximum settingto allow the node to broadcast at maximized range assuming a clearenvironment. Such a setting provides a known anticipated range distance.In the example of FIG. 13, master node M1 910 a may be broadcasting at amaximum power level P1 that reaches a first range distance from node M1.However, if node M1 is known to be within an adverse RF shieldingenvironment, the first anticipated range distance may be a distanceadjusted to account for the contextual environment of such shielding(e.g., a type of context data). Anticipated range distances may beadjusted depending upon one or more types of relevant context (e.g., oneor more types of context data related to how an RF output signal fromthe node may be impeded).

At step 2910, method 2900 identifies which of the nodes associated withthe first node received at least one of the first messages. In oneembodiment, the first node may be able to access and review associationdata in its onboard memory storage as part of identifying which are thenodes associated with it. In one example, the associations with thefirst node may be passive associations (e.g., not actively paired andsecurely connected) or active associations (e.g., actively paired andable to securely connect and share data), or a combination of both typesof associations.

Next, at step 2915, the first node broadcasts one or more secondmessages at a second anticipated range distance, which is incrementallysmaller than the first anticipated range distance. In the example ofFIG. 13, master node M1 910 a may be the first node and now isbroadcasting at a medium power level P2 that reaches a secondanticipated range distance from node M1. By incrementally changing theRF power level in this manner, master node M1 910 a now no longer canreach nodes C-E as shown in FIG. 13.

At step 2920, method 2900 concludes by determining a location of one ormore of the identified associated nodes that did not receive any of thesecond messages but received at least one of the first messages, wherethe location is between the first and second anticipated range distancesfrom the first node. Again, in the example of FIG. 13, master node M1910 a may determine the location of nodes C-E (given they did notreceive the message sent out the second anticipated range distance at RFpower level P2) to between the first anticipated range distance (whenmaster node M1 was broadcasting at power level P1) and the secondanticipated range distance (when master node M1 was broadcasting atpower level P2) from the known location of master node M1.

In one embodiment, the method 2900 may also have the first nodebroadcasting one or more third messages at a third anticipated rangedistance (incrementally smaller range than the second anticipated rangedistance), and determining a location of one or more of the identifiedassociated nodes that did not receive any of the third messages butreceived at least one of the second messages, where the location isapproximately near the second anticipated range distance from the firstnode. Again, in the example of FIG. 13, by incrementally changing thepower level down to P1 and broadcasting a third message at ananticipated range distance for that P1 level, the master node M1 candetermine the location of node A (as node A received the second messagebut did not receive the third message) to be approximately near theanticipated range distance for P2 from the location of master node M1.

Additional embodiments of method 2900 may also refine such determinedlocations by updating the location of the first node. In one embodiment,the first node may be a mobile node. As such, refining may involvedetermining a current mobile location of the first node, and refiningthe location of the one or more of the identified associated nodes thatdid not receive any of the second messages but received at least one ofthe first messages based upon the current mobile location of the firstnode. Thus, as the first node moves and updates its own location (e.g.,via GPS signals received by location circuitry 475 on a master node),the first node is able to leverage its own updated location andadvantageously refine the location of nodes associated with it.

And, in some embodiments, the refined location of associated nodes maybe transmitted to a server. This provides an update to the server, andaids in tracking and managing the location of nodes in the network.Again, referring back to the example of FIG. 13, master node M1 910 amay take advantage of such a method for locating associated nodes, suchas the locations of ID nodes A-E 920 a-920 e, and update server 100 withthis new location data related to the current location of node M1 andany of the nodes associated with node M1.

Those skilled in the art will appreciate that method 2900 as disclosedand explained above in various embodiments may be implemented on a node(e.g., master node 110 a in FIG. 4, master node M1 910 a in FIG. 13, ormaster node M1 2210 a in FIG. 22A) running one or more parts of mastercontrol and management code 425 (e.g., the location aware/capturemodule). Such code may be stored on a non-transitory computer-readablemedium, such as memory storage 415 on master node 110 a. Thus, whenexecuting code 425, the master node's processing unit 400 may beoperative to perform operations or steps from the exemplary methodsdisclosed above, including method 2900 and variations of that method.

In another embodiment, a node apparatus is described in a wireless nodenetwork that uses location determination by association as describedwith reference to the steps related to method 2900. As mentioned above,such as node apparatus may be implemented with a master node having anode processing unit, a node volatile memory, a node memory storage, anda first and second communication interface. Each of the memories andcommunication interfaces are coupled to the node processing unit.Further, the node memory storage maintains at least a program codesection, association data, and location data and, at times, shippinginformation. The first communication interface provides a firstcommunication path operatively coupling the node with a plurality ofother nodes in the network, while the second communication interfaceprovides a second communication path operatively and separately couplingthe node with a server in the network.

In this embodiment, the node processing unit is operative to transmitone or more first messages via the first communication interface at afirst anticipated range distance, and identify which of the others nodesthat are associated with the first node received at least one of thefirst messages. In one embodiment, the node processing unit may beoperative to access the association data in the node memory storage whenidentifying which of the nodes associated (e.g., passive, active, orboth types of associations) with the first node received at least one ofthe first messages.

The first anticipated range distance may be an optimal transmissionrange for the first communication interface and, in a more detailedexample, may be adjusted based upon context data (e.g., RF shieldinginherent from the surrounding environment of the node). In yet anotherembodiment, the first anticipated range distance and the secondanticipated range distance may be adjusted based upon one or more typesof context data related to how an RF output signal transmit from thefirst communication interface may be impeded by an environment of thenode.

The node processing unit is also operative to transmit one or moresecond messages via the first communication interface at a secondanticipate range distance (incrementally smaller than the firstanticipated range distance) and determine a location of one or more ofthe identified associated nodes that did not receive any of the secondmessages but received at least one of the first messages. That locationis between the first anticipate range distance from a known location ofthe node and the second anticipated range distance from the knownlocation of the node. In a further example, the node processing unit maybe operative to store the determined location in the node memory storageas part of the location data.

The node processing unit may also be operative to transmit one or morethird messages via the first communication interface at a thirdanticipated range distance (incrementally smaller range than the secondanticipated range distance) and determine a location of one or more ofthe identified associated nodes that did not receive any of the thirdmessages but received at least one of the second messages, where thelocation is between the second anticipated range distance from the knownlocation of the node and the third anticipated range distance from theknown location of the node.

In another embodiment, the node may be mobile and the node processingunit may be further operative to refine the location of the one or moreof the identified associated nodes that did not receive the secondmessage but received the first message by updating a location of thefirst node. In more detail, the node processing unit may be operative todetermine a current mobile location of the first node (e.g., check withlocation circuitry onboard the node for valid GPS signals and a locationlock based on such signals), and refine the location of the one or moreof the identified associated nodes that did not receive any of thesecond messages but received at least one of the first messages basedupon the current mobile location of the first node. The node processingunit may also be operative to transmit the refined location to theserver over the second communication interface.

Location Determination Through ID Node Advertise

While FIG. 13 provides an example of location determination throughmaster node advertising, FIG. 14 focuses on location determinationthrough ID node advertising. In particular, FIG. 14 is a diagramillustrating an exemplary location determination using ID node advertisein accordance with an embodiment of the invention. In the illustratedembodiment shown in FIG. 14, exemplary ID node F 920 f is in anadvertising mode but is without a known location. As with FIG. 13, FIG.14 illustrates the exemplary different RF output power levels from IDnode F 920 f as concentric ranges 1405-1415 about ID node F 920 f. Thus,ID node F 920 f may broadcast at a maximum power P1, related to range1405, but may control the RF output power level and dynamically changethe RF output power level to P2 and broadcast at a smaller range 1410,or to P3 and broadcast to an even smaller range 1415. Master nodes M1-M3910 a-910 c are disposed in various known locations relatively near IDnode F 920 f, which has an unknown location. As such, ID node F 920 fmay take advantage of the ability to adjust an RF characteristic, suchas RF output signal power level, of its own short-range communicationinterface as part of how the system may determine location of ID node Fthrough ID node advertising.

In the illustrated embodiment, an RF output signal power level of IDnode F 920 f may be varied or dynamically adjusted via programmablesettings (such as profile settings or parameters) related to operationsof variable power short range communication interface 375. Additionally,while an actual communication range may vary with the surroundingenvironment, a maximum anticipated communication range of the ID node'stransmitter at each power level is known assuming an optimal operatingenvironment or no substantial RF shielding or interference. Thus, aparticular power level setting for a broadcasting node is inherentlyassociated with a corresponding anticipated range distance.

In an exemplary method of determining a nodes location using ID nodeadvertising, the RF output signal power level may be varied acrossmultiple power levels to improve location through master nodeassociation. In more detail, when the ID node F's variable power shortrange communication interface 375 is set to P1, its maximum output, IDnode F 920 f is seen by each of master nodes M1-3 910 a-910 c. Theanticipated open air performance or range distance (optimal range, orrange based upon analytics or historic measurements) of the radio in IDnode F's variable power short range communication interface 375 at P1power level may have been previously been found to be approximately 30feet. Thus, without any examination of RSSI levels from the individualmaster nodes, the system knows ID Node F is within 30 feet of masternodes M1-M3.

Next, when the ID node F's variable power short range communicationinterface 375 is set to P2, a medium output level in this example, IDnode F 920 f is seen by master nodes M1 910 a and M2 910 b. Theanticipated open air performance or range distance (optimal range, orrange based upon analytics or historic measurements) of the radio in IDnode F's variable power short range communication interface 375 atrunning at P2 power level is approximately 15 feet. Thus, without anyexamination of RSSI levels from the individual nodes, we know masternodes M1 910 a and M2 910 b are within 15 feet of ID node F 920 f inthis example. Furthermore, we know the master node no longer receivingthe broadcasted RF signal from ID node F 920 f (e.g., master node M3 910c) is somewhere within 30 feet of ID node F 920 f, but probably morethan 15 feet away from node F in this example.

And when ID node F's variable power short range communication interface375 is set to P3, its minimum output level in this example, ID node F920 f is seen by only master node M2 910 b. The anticipated open airperformance or range distance (optimal range, or range based uponanalytics or historic measurements) of the radio in ID node F's variablepower short range communication interface 375 at P3 power level isapproximately 5 feet. Thus, without any examination of RSSI levels fromthe master nodes, we know the location of ID node F 920 f is within 5feet of the known location of master node M2 910 b in this example.

The ranging steps with respect to the changed RF characteristics of anadvertising ID node, as discussed in the example above, may then berepeated for any of the identified nodes in order to building a morecomplete picture of the relative location of each node.

Furthermore, the timing between such ranging steps may vary dynamicallydepending upon whether the node is moving. Those skilled in the art willappreciate that when moving, a quicker flow through such ranging stepswill help to provide better accuracy given the movement of nodes. Thus,the time interval between instructing a node to broadcast one or moremessages at a particular power level and then instructing that node tobroadcast one or more messages at a different power level may be desiredto be shorter when the node is moving, which can be determined basedupon context data. For example, the context data may indicate the nodeis within a node package an on a moving conveyor system. As such, thenode is moving relative to fixed master nodes that may be positionedalong the conveyor system. Thus, server may have the first node performthe ranging steps where power is varied in relative quick successioncompared to a situation where the context data indicates the node is notmoving or is substantially stationary.

FIG. 30 is a flow diagram illustrating another exemplary method forlocation determination using one or more associations of nodes in awireless node network in accordance with an embodiment of the invention.Referring to FIG. 30 and how it explains a particular way to locate anode using associations and master node one or more master nodeadvertising techniques, method 3000 begins at step 3005 by instructing afirst of the nodes to broadcast one or more first messages at a firstpower level, the first power level being related to a first anticipatedrange distance. In one example, the first anticipated range distance maybe an optimal range for the first of the nodes (e.g., a transmissionrange that assumes there are no obstructions and a clear signal pathbetween nodes). In another example, the first anticipated range distancemay be an optimal range for the first node adjusted based upon contextdata (e.g., data related to the surrounding RF environment of the firstnode).

At step 3010, the method 3000 identifies which of the nodes associatedwith the first node have known locations at step 3010. For example, thistype of identification may be accomplished by reviewing association datathat indicates which of the nodes are associated with the first node(e.g., via passive association, via active association, or via acombination of both), determining which of the nodes are associated withthe first node based upon the reviewed association data, and identifyingwhich of those associated nodes have known locations.

The method 3000 continues at step 3015 by determining which of theidentified associated nodes received at least one of the first messages.Next, the method 3000 instructs the first node at step 3020 to broadcastone or more second messages at a second power level, where the secondpower level is related to a second anticipated range distance and thesecond power level incrementally smaller than the first power level. Ina further example, the first anticipated range distance and the secondanticipated range distance may be adjusted based upon one or more typesof context data related to how an RF output signal from the first nodemay be impeded.

At step 3025, method 3000 determines which of the identified associatednodes received at least one of the second messages. Method 3000concludes at step 3030 where the method determines a location of thefirst node to be at or between the first anticipated range distance andthe second anticipated range distance from each of the identifiedassociated nodes that did not receive at least one of the secondmessages but received at least one of the first messages.

As mentioned above, determining the node's location may be improved whenaccounting for movement. As such, an embodiment of method 3000 mayinstruct the first node to broadcast the one or more second messageswithin a time interval after instructing the first node to broadcast theone or more first messages. The time interval may be predetermined insome implementations, but also may be a dynamically set parameter inother implementations based upon context data related to the first node.In more detail, the time interval may be reduced from a prior value whenthe context data related to the first node indicates the first node ismoving, but may be increased from a prior value when the context datarelated to the first node indicates the first node is substantiallystationary.

In another embodiment, method 3000 may further include instructing thefirst node to broadcast one or more third messages at a third powerlevel. Such a third power level is related to a third anticipated rangedistance and incrementally smaller range than the second anticipatedrange distance. Thereafter, the method may determining the location ofthe first node to be at or between the second anticipated range distanceand the third anticipated range distance from each of the identifiedassociated nodes that did not receive any of the third messages butreceived at least one of the second messages.

In another embodiment, method 3000 may comprise refining the location ofthe first node with an updated location of one or more of the identifiedassociated nodes that did not receive at least one of the secondmessages but received at least one of the first messages. For example,if the first node is associated with a mobile master node, the locationof the first node may be refined with an updated location of the mobilemaster node (which may be closer to the first node than previouslydetermined).

In a further embodiment, the first node in the operation of method 3000may not be self-aware of its own location. In another embodiment, thefirst node in the operation of method 3000 may have been previouslyself-aware of the location of the first node but may no longer beself-aware of the location of the first node prior to broadcasting theone or more first messages. In more detail, the first node may no longerbe self-aware of the location of the first node prior to broadcastingthe first message because of a change in the environment surrounding thefirst node. Such a change in the environment may be, for example, whenthe first node has moved inside a structure (e.g., building, vehicle,aircraft, container, etc.) that blocks location signals from beingreceived by the first node.

Those skilled in the art will appreciate that method 3000 as disclosedand explained above in various embodiments may be implemented on a node(e.g., master node 110 a in FIG. 4) running one or more parts of mastercontrol and management code 425 (e.g., the location aware/capturemodule) to control operations of an ID node (such as ID node F in FIG.14) as part of location determination via ID node advertising. Such codemay be stored on a non-transitory computer-readable medium, such asmemory storage 415 on master node 110 a. Thus, when executing code 425,the master node's processing unit 400 may be operative to performoperations or steps from the exemplary methods disclosed above,including method 3000 and variations of that method.

From an apparatus perspective, an exemplary node apparatus in a wirelessnode network that uses location determination by association maycomprises a node processing unit, node memory coupled to and used by thenode processing unit (e.g., a node volatile memory and a node memorystorage). The node memory storage maintains at least a program codesection, association data, and location data. The node apparatus furtherincludes a first communication interface that provides a firstcommunication path coupled to the node processing unit and operativelycoupling the node with a plurality of other nodes in the network. Forexample, the master node 110 illustrated in FIG. 4 includes such typesof operational structure.

The node processing unit (e.g., processing unit 400 of master node 110a), when executing at least the program code section resident in thenode volatile memory, is operative to perform specific functions orsteps. In particular, the node processing unit is operative tocommunicate an instruction to a first of the other nodes (e.g., an IDnode or master node temporarily operating as an ID node) via the firstcommunication interface to cause the first other node to broadcast oneor more first messages at a first power level, where the first powerlevel is related to a first anticipated range distance.

The first anticipated range distance may be an optimal range for thefirst of the nodes and, in more detail, an optimal range for the firstof the nodes adjusted based upon context data. In even more detail, thefirst anticipated range distance and the second anticipated rangedistance may be adjusted based upon one or more types of context datarelated to how an RF output signal broadcast from the first node may beimpeded.

The node processing unit is also operative to identify which of thenodes associated with the first node have known locations. To do this,the node processing unit may access and review association data storedon the node memory storage (e.g., data indicating what nodes arepassively or actively associated with the first other node), maydetermine which of the remaining other nodes are associated with thefirst other node based upon the reviewed association data, and mayidentify which of the remaining other nodes determined to be associatedwith the first other node have known locations.

The node processing unit is also operative to determine which of theidentified associated nodes received at least one of the first messages,and to communicate another instruction via the first communicationinterface to the first node to cause the first node to broadcast one ormore second messages at a second power level, where the second powerlevel being is to a second anticipated range distance and incrementallysmaller than the first power level.

Finally, the node processing unit is operative to determine which of theidentified associated nodes received at least one of the secondmessages, and then determine a location of the first node to be at orbetween the first anticipated range distance and the second anticipatedrange distance from each of the identified associated nodes that did notreceive at least one of the second messages but received at least one ofthe first messages.

In a further embodiment, the node processing unit may be operative tocommunicate a third instruction via the first communication interface tothe first node to cause the first node to broadcast one or more thirdmessages at a third power level. The third power level is related to athird anticipated range distance and incrementally smaller range thanthe second anticipated range distance. Additionally, the node processingunit may then be operative to determine the location of the first nodeto be at or between the second anticipated range distance and the thirdanticipated range distance from each of the identified associated nodesthat did not receive any of the third messages but received at least oneof the second messages.

In still another embodiment, the node processing unit is able to accountfor movement of the first node with a time interval between instructionssent to the first node. In particular, the node processing unit may befurther operative to communicate another instruction via the firstcommunication interface to the first node to broadcast the secondmessages within a time interval after instructing the first node tobroadcast the first messages. In a more detailed example, the timeinterval may be dynamically set based upon context data related to thefirst node. In even more detail, the time interval may beprogrammatically reduced from a prior value when the context datarelated to the first node indicates the first node is moving (e.g., thefirst node is on a moving conveyor system) and/or the time value of theinterval may be increased from a prior value when the context datarelated to the first node indicates the first node is substantiallystationary (e.g., the node is within a node package recently placed in astorage area).

The node processing unit, in a further embodiment, may be operative torefine the location of the first other node with an updated location ofone or more of the identified associated nodes that did not receive atleast one of the second messages but received at least one of the firstmessages, and cause a second communication interface (e.g., medium/longrange communication interface 485 coupled to processing unit 400) totransmit the refined location to the server.

From a server perspective, FIG. 31 is a flow diagram (similar to FIG.30) illustrating yet another exemplary method for location determinationusing one or more associations of nodes in a wireless node network inaccordance with an embodiment of the invention. Those skilled in the artwill appreciate that while a server may operate to implement the stepsas laid out in method 3000 and discussed above, FIG. 31 provides moredetails as to how a server processing unit (such as processing unit 500running server code 525) may implement such a method at that level ofthe network via method 3100. In this more detailed embodiment, theserver is communicating directly with a master node (e.g., a first node)to direct and control how the master node interacts with and causesoperations to be undertaken on the ID node (e.g., a second node). Thus,step 3105 is similar to step 3005 but more precisely calls forcommunicating with a first node via a communication interface to cause asecond node in the network to broadcast one or more first messages at afirst power level at the request of the first node, where the firstpower level is related to and corresponds with a first anticipated rangedistance. Likewise, step 3120 is similar to step 3020 but more preciselycalls for communicating with the first node via the communicationinterface to cause the second node to broadcast one or more secondmessages at a second power level at the request of the first node, thesecond power level being related to a second anticipated range distanceand incrementally smaller than the first power level. The other steps ofmethod 3100 are similar to those illustrated and explained aboverelative to method 3000, and that the similar principles will apply tomethod 3100.

Those skilled in the art will appreciate that method 3100 as disclosedand explained above in various embodiments may be implemented on aserver (e.g., server 100 in FIG. 5) running one or more parts of servercontrol and management code 525 to direct a master node to controloperations of an ID node (such as ID node F in FIG. 14) as part oflocation determination via ID node advertising. Such code may be storedon a non-transitory computer-readable medium, such as memory storage 515on server 100. Thus, when executing code 525, the server's processingunit 500 may be operative to perform operations or steps from theexemplary methods disclosed above, including method 3100 and variationsof that method.

And similar to the node apparatus described above, one embodimentincludes an exemplary server apparatus in a wireless node network thatuses location determination by association. The exemplary serverapparatus generally comprises a server processing unit, server memorycoupled to and used by the server processing unit (e.g., a servervolatile memory and a server memory storage). The server memory storagemaintains at least a program code section, association data, andlocation data. The server apparatus further includes a communicationinterface coupled to the server processing unit and that provides accessto a communication path operatively coupling the server with at least afirst node in the network.

The exemplary server processing unit, when executing at least theprogram code section resident in the server volatile memory, isoperative to perform specific functions or steps. In particular, theserver processing unit is operative to communicate with the first nodevia the communication interface to cause a second node in the network tobroadcast one or more first messages at a first power level at therequest of the first node, where the first power level is related to afirst anticipated range distance; identify which of the remaining nodesin the network associated with the second node have known locations;determine which of the identified associated nodes received at least oneof the first messages; communicate with the first node via thecommunication interface to cause the second node to broadcast one ormore second messages at a second power level at the request of the firstnode, where the second power level is related to a second anticipatedrange distance and incrementally smaller than the first power level;determine which of the identified associated nodes received at least oneof the second messages; and determine a location of the second node tobe at or between the first anticipated range distance and the secondanticipated range distance from each of the identified associated nodesthat did not receive any of the second messages but received at leastone of the first messages. And in a further embodiment, the serverapparatus' processing unit may be further operative to store thedetermined location in the server memory storage as part of the locationdata.

In another embodiment, the server apparatus' processing unit may beoperative to communicate with the first node via the communicationinterface to cause the second node to broadcast the one or more secondmessages within a time interval after communicating with the first nodeto cause the second node to broadcast the one or more first messages. Aspreviously mentioned, this type of time interval may dynamically setbased upon context data related to the second node. Context data mayalso be used as set forth above with respect to the node apparatus butapplied here to the second node—such was where the first anticipatedrange distance is the optimal range for the second node adjusted basedupon context data.

Master Node Location Determination Through Advertise

In another embodiment, a master node may no longer know its location.For example, such a situation may occur when a master node determinesit's current location via GPS location circuitry 475, but the masternode finds itself without access to an adequate number of GPS signals(e.g., it cannot determine a location due to the lack of a sufficientnumber of GPS signals from diverse GPS satellites). Such a situation mayhappen when the master node moves indoors is proximate to a structurethat interferes with the location signals.

In an exemplary embodiment where a master node attempts to determine itsown location via advertising techniques, the master node may detect aloss of location confidence (e.g., upon a loss of detected GPS signals;upon detecting a separate signal to processing unit 400 indicating themaster node's location is unknown; when processing unit 400 sensesmovement (e.g., via accelerometers (not shown) or the like) but cannotconfirm that the location circuitry 475 is providing updated locationinformation for the node, etc.). In other words, the master node becomesaware that it no longer has a known location.

Next, the master node responds by beginning to broadcast one or moreadvertising messages in a similar way as ID node F 920 f is described asdoing with respect to FIG. 14. This is done so that the master nodehaving an unknown location can advantageously leverage off the knownlocations of nearby other nodes. As such, an embodiment may allow a typeof leveraged chaining effect whereby known locations of particular typesof nodes may be used to extend location information to other nodes thatdo not know their locations (e.g., ID nodes) or nodes that have detecteda loss of location confidence (e.g., master nodes). Thus, such anembodiment may be used to determine an indoor location of a master node(including equipment equipped with master node functionality) in caseswhere signals for the conventional onboard location circuitry 475 arenot available.

Referring back to the exemplary method 3000 and FIG. 30, method 3000 maybe such that the first node is not self-aware of the location of thefirst node. This may happen when the first node (e.g., an ID node) isactually a master node that was previously self-aware of its ownlocation (e.g., via received GPS signals) but is no longer self-aware ofits location (e.g., when the GPS signals can no longer be received),which has the master node changing operation to operate as an ID nodeprior to broadcasting the first message. In other words, the master nodemay no longer be self-aware of its location and begin operating as an IDnode for purposes of location determination prior to broadcasting thefirst message because of a change in the environment surrounding themaster node, such as when the master node has moved inside a structurethat blocks location signals from being received by the master node.Thus, an embodiment may advantageously allow a node to adaptively alteroperations when moving from a clear outdoor environment to an indoorenvironment. And a server may interact with such a master node whilethat master node is operating, for location purposes, as an ID node,temporarily.

Location with Improved RSSI Measurements

In another embodiment, a signal strength measurement between two or morenodes may be used to determine the proximity of the nodes by using oneor more improvements to conventional RSSI measurements. In conventionalRSSI measurements, such as with Bluetooth 4.0, those skilled in the artwill appreciate that adaptive frequency hopping as part of spreadspectrum techniques may cause undesirably cause the signal strength tofluctuate. In other words, the advantage of using frequency hopping andspread spectrum for security and avoidance of interference may have anegative impact on using such signals for stable proximity-basedlocation determinations. Thus, it may be desired to emphasize stabilityof a signal and limits to fluctuation for purposes of locationdetermination.

In one embodiment, a type of improvement for RSSI measurements mayinclude reducing the number of channels and/or a corresponding frequencyrange in use during advertising from nodes. For example, a node may haveprocessing unit 300/400 adaptively control variable power short rangecommunication interface 375/480 to reduce the number of channels and/orthe frequency range used during node advertising. Such a dynamic changemay be implemented, in some embodiments, by altering the content of aparticular type of profile data 330/430, such as an RF profile data thateffectively defines RF characteristics of a node (e.g., frequency, powerlevel, duty cycle, channel numbers, channel spacing, alternativefluctuation modes, etc.). In one further embodiment, a first fluctuationmode may be defined that provides a default or more standardcommunication protocol, such as the conventional frequency hopping,spread spectrum, and channel allocations for Bluetooth® communications.Other alternative modes (one or more) may be defined that alter one ormore RF characteristics to provide increasingly more stable and lessfluctuations of the RF output signal from a node. Thus, a node may bedynamically placed into one or more modes regarding such RFcharacteristics that increasingly emphasize stability of the node's RFoutput signal and limits fluctuation for purposes of enhanced locationdetermination using RSSI measurements.

In another embodiment, a type of improvement for RSSI measurements mayinclude ensuring visibility to and advantageously managing automaticgain control (AGC) circuitry (not shown) that may cause the RF outputsignal to vary for a node. For example, a node may include a type of AGCcircuitry as part of variable power short range communication interface375/480. This type of AGC circuitry may allow node processing unit300/400 or other logic circuitry that is part of variable power shortrange communication interface 375/480 to limit fluctuations undercertain conditions (e.g., when attempting to use RSSI locationdetermination techniques). In this example, different AGC circuitrysettings may be defined in exemplary RF profile data that effectivelydefines RF characteristics of a node (e.g., frequency, power level, dutycycle, channel numbers, channel spacing, alternative fluctuation modes,etc.). This is yet another example of how a node may be dynamicallyplaced into one or more modes regarding such RF characteristics(including AGC circuitry settings) that increasingly emphasize stabilityof the node's RF output signal and limits fluctuation for purposes ofenhanced location determination using RSSI measurements.

Location with Adjustments for Environmental Factors in RF Signal Quality

In general, those skilled in the art will appreciate that environmentalfactors may cause a communication signal, such as an RF signal, tofluctuate or be transmitted and received in a manner that undesirablyvaries depending upon a signal path environment. Passive physicalinterference factors (e.g., forms of electronic signal shielding) may besubstantially close and cause drops in signal strength across the outputranges of the nodes. Additionally, active radio interference factors mayvary across the RF output ranges of the nodes depending upon otheractive devices in the reception vicinity. Thus, the proximateenvironment of a node may have a multitude of adverse factors thatimpact communications and, as a result, the ability to locate the node.

In one embodiment, making location determinations may be enhanced by adata analytics type of approach that may adjust and account fordifferent RF environmental factors for a similar type of node in asimilar type of situation. For example, the quality of the RF outputsignal of a particular type of node and the corresponding physical rangeof that signal to a receiver of known sensitivity may be determined fora given environment. In this example, the system defines a maximum rangeof that signal based on a predetermined condition, such as open-airconnectivity. This may assume an environment with no signal degradationdue to interference or physical shielding. However, both interferenceand physical shielding may diminish the range of the RF output signal ofa node. In a dynamically adaptive and learning manner, the system maycollect information on how a particular type of node may operate in aparticular environment under certain settings (e.g., reported signalstrengths and corresponding settings for RF output signal power levels).This analysis of a similar environment may be repeated. In other words,through such data analytics of an anticipated environment to be faced bya similar node, signal loss information can be generated and applied asa type of context data (i.e., RF data) for a node in a similarenvironment to refine location determination. Thus, an exemplaryembodiment may refine location determinations with adaptive signal losscharacteristics based on a contextual appreciation of an anticipatedenvironment (e.g., physical shielding such as packaging, packagecontents, proximate package, proximate package contents, and physicalinfrastructure causing signal variance) without requiring a calibrationphase.

And advantageously combining those data points with 3^(rd) party datadescribing the physical environment, in which the node was located in atthat time, may refine location even further. Such information may beused as RF data (a type of context data) in future efforts to manage andlocate a similar type of node anticipated to be in a similarenvironment.

In more detail, in an embodiment that refines a location determinationbased upon context and data analytics to adjust for known RFimpediments, the maximum physical range of a node's RF output signalrelative to a receiver of known RF sensitivity is determined. In oneexample, this first range value may be referred to as a theoretical ornominal open-air range of a similar type transmitter-receiver node pairin a similar environment but with substantially no physical shielding orsignal interference negatively impacting the signal range. A secondrange value, which may be considered an actual RF range value, may bethe observed range of the signal in a similar environment but wherethere are contextual factors reducing the communication range, includingphysical shielding due to factors like packaging, package contents,proximate package, proximate package contents, physical infrastructure,interference from other radio sources, or shipper specific informationsuch as vehicle or facility layout information. Through access to priordata analysis of the differing range values and with knowledge of theoperational environment of the transmitting node was in (e.g., a similarenvironment to the proximate environment of the node), a refinedlocation may be determined using an approximation of an actual RF outputrange that intelligently adjusts what may be anticipated to be the RFenvironment of the node. In other words, by knowing the appropriatecontextual environment related to a node (such as signal degradationinformation on how a similar node operates in a similar environment), animproved location determination may be made to make intelligent yetefficient adjustments (such as communication distance adjustments) thatprovide a refined location of the node.

In one example, such as the example shown in FIG. 2, master node 110 bis outside of a container (such as a Uniform Load Device (ULD) container210 known to be used for transporting groups of items on aircraft) thathas an ID node inside the container. A first or theoretical range valuebetween master node 110 b and ID node 120 b may be determined to be 10feet at a specific RF output power level when the package (and relatedID node) may be known to be less than 10 feet away from the scanningnode (e.g., master node 110 b). A second range value at similardistances with similar types of nodes, but with incident RF signal lossas a result of communicating through the wall of the container 210, maybe between 4 and 5 feet. If context data, such as 3^(rd) partyinformation or scan data, indicates the transmitting node is within theULD container 210, the system would expect the transmission range to belimited according to the data analytics associated with this known RFimpediment (e.g., characteristics for transmitting through ULD container210), thus reducing the possible scanning nodes that may see thebroadcasting node within the ULD container, or require the transmittingnode to increase its RF output power to be heard.

FIG. 32 is a flow diagram illustrating an exemplary method for locationdetermination of a first node in a wireless node network based oncontext data in accordance with an embodiment of the invention.Referring now to FIG. 32, method 3200 begins at step 3205 with a networkdevice (such as a master node or server) accessing a first type of thecontext data related to a proximate environment of the first node.

The first type of context data comprises signal degradation informationon how a second node would operate in a similar environment to theproximate environment of the first node when the second node is asimilar type as the first node. Thus, rather than calibrating with anactual measurement relative to the current proximate environment of thefirst node, the signal degradation information provides compensationinformation on what may be generally anticipated in a more generalproximate environment based on how a similar type of node may operate ina similar environment. As the similar environment of the similar node isgenerally an approximation for what is anticipated to be the proximateenvironment of the first node, this advantageously avoids the need foran actual calibration of the proximate environment. In one embodiment,the signal degradation information may be based upon a difference in howthe second node communicates when exposed to an adverse communicationenvironment (such as a similar environment to the proximate environmentof the first node) compared to how the second node would communicateswhen exposed to a nominal communication environment (such as anenvironment that is unencumbered by shielding and interference factors).Those skilled in the art will appreciate that a nominal communicationenvironment need not be perfectly clear of all influences that shield orinterfere with communications.

The types and aspects of signal degradation information may varydepending on a wide variety of factors. In one embodiment, the signaldegradation information may be related to at least one of shielding andinterference. Thus, signal degradation information may include bothpassive and active factors that impact the communication environment.

In another embodiment, the signal degradation environment may be basedupon a degraded operation of the second node when the similarenvironment is an adverse communication environment. In more detail, thesignal degradation information may be based upon a difference in how thesecond node communicates when exposed to the adverse communicationenvironment compared to how the second node communicates when exposed toa substantially normal communication environment, such as an open airenvironment.

In still another embodiment, signal degradation information may relateto at least shipment data for one or more items being shipped (e.g.,currently shipped or shipped in the past) and located in the proximateenvironment of the first node. For instance, a package near the firstnode may include metallic materials that may impede or block RF signalsand the signal degradation information may relate to such informationabout close packages being shipped near the first node. In anotherexample, the signal degradation information may relate to at leastlayout data for one or more physical structures in the proximateenvironment of the first node. In more detail, the layout data may befor one or more physical structures (e.g., walls, machinery, enclosures,and conveyances) in the proximate environment of the node near apredicted path for the first node. In yet another example, the signaldegradation information relates to at least historic data on one or moreanalyzed prior operations of the second node.

At step 3210, the network device, such as a master node or server, mayadjust an anticipated communication distance related to the first nodebased upon on the first type of the context data. In one example, theanticipated communication distance may be a theoretical broadcastdistance based upon parameters of the device's radio. Such ananticipated communication distance is known as it is an estimate of theradio's range. In one example, the adjusted communication distancecomprises an anticipated reduced range distance for a transmission fromthe first node. In another example, the adjusted communication distancecomprises an anticipated reduced receiver sensitivity distance for thefirst node.

In yet another example, adjusting the communication distance may beaccomplished by adaptively adjusting, by the network device, thecommunication distance based upon the signal degradation information anda second type of the context data. In other words, the communicationdistance may be adjusted based upon signal degradation informationconsidered along with other types of context data, such as how the firstnode is being moved (such as an anticipated movement of the first nodealong a predicted transit path for the first node) or a density of othernodes near the first node.

At step 3215, the network device determines the location of the firstnode based upon the adjusted communication distance. In a furtherembodiment, the method may also update the adjusted communicationdistance by the network device based upon movement of the first node,and may refine the location of the first node with an updated adjustedcommunication distance. This may happen with the first node is a mobilemaster node capable of self-determining its own location.

Those skilled in the art will appreciate that method 3200 as disclosedand explained above in various embodiments may be implemented on anetwork device (e.g., exemplary master node 110 a in FIG. 4 or server100 in FIG. 5) running one or more parts of their respective control andmanagement code to perform steps of method 3200 as described above. Suchcode may be stored on a non-transitory computer-readable medium, such asmemory storage 415 on master node 110 a or memory storage 515 on server100. Thus, when executing such code, the respective network device'sprocessing unit may be operative to perform operations or steps from theexemplary methods disclosed above, including method 3200 and variationsof that method.

In more detail, an exemplary network device apparatus for determining alocation of a first node in a wireless node network based on contextdata, the exemplary network device may include a processing unit, avolatile memory coupled to the processing unit, and a memory storagecoupled to the processing unit. The exemplary network device furtherincludes a communication interface coupled to the processing unit andthat provides a communication path operatively coupling the networkdevice with the first node in the network.

The memory storage for the device maintains at least a program codesection and context data having at least signal degradation information.Such signal degradation information, as a type of context data, isinformation on how a second node would operate in a similar environmentto a proximate environment of the first node when the second node is asimilar type as the first node. Examples of signal degradationinformation may include those discussed above relative to step 3205 ofmethod 3200.

When executing at least the program code section when resident in thevolatile memory, the processing unit of the network device is operativeto perform the steps noted and described above with respect to method3200. In more detail, the processing unit is operative to at leastconnect with the memory storage to access the signal degradationinformation, adjust a communication distance (if needed) related to thefirst node based upon on the signal degradation information, determinethe location of the first node based upon the adjusted communicationdistance, and store the determined location of the first node aslocation data on the memory storage.

Adjusting the communication distance by the processing unit may beaccomplished as described above with regard to step 3210 of method 3200.And as mentioned above, the processing unit may be further operative toadaptively adjust the communication distance where other types ofcontext data are also considered, such as movement and anticipated nodemovement as detailed out above.

In a further embodiment, the network device may be a mobile master nodethat includes location circuitry (such as GPS circuitry 475 of exemplarymaster node 110 a shown in FIG. 4). In this embodiment, the processingof the network device may be further operative to determine a locationof the network device based upon an output signal from the locationcircuitry received by the processing unit, and determine the location ofthe first node based upon the adjusted communication distance and thelocation of the network device. As such, the first type of the contextdata related to the proximate environment of the first node is basedupon the determined location of the first node.

Those skilled in the art will also appreciate that in some operationalenvironments, the signal degradation information may not require anyadjustment to the communication distance in an embodiment. However, inother environments (e.g., adverse RF environments), the signaldegradation information may provide a basis for adjusting thecommunication distance in the embodiment, even if not performed everytime. Thus, an adjustment to the communication distance may not beneeded in all proximate environments of the first node but may beperformed, if needed, based on the proximate environment of the firstnode. It is the ability of an embodiment to adjust this communicationdistance when needed and if needed that advantageously allows forlocating the first node with more accuracy.

Location Through Triangulation

In some embodiments, various methods for determining a node's locationmay rely upon, at least in part, triangulation techniques. In otherwords, as the wireless node network collects data onreceiver-transmitter pairs, other methods for determining location ofthe individual nodes that utilize triangulation, at least in part, maybecome possible. FIG. 15 is a diagram illustrating an exemplary locationdetermination through triangulation within a wireless node network inaccordance with an embodiment of the invention. Referring now to theillustrated embodiment of FIG. 15, three exemplary master nodes M1-M3910 a-910 c are shown with each master node having a known location.Exemplary ID nodes A-E 920 a-920 e are also shown where they are atleast in communication range of one or more of exemplary master nodesMA-M3 910 a-910 c.

In this illustrated example, the master nodes M1-M3 may detect andcollect advertising messages from ID nodes A-E at varying and knownpower levels. The captured information is forwarded by the master nodesM1-M3 to the backend server 100, where location determinations may bemade. For example, factors like RSSI and visibility of each node at eachpower level may be used to determine, with a higher degree of accuracy,the location of nodes where sufficient information is available.

For an exemplary system to triangulate a node, three nodes with knownlocations must have seen the broadcasting node. In this example, twoadvertising ID nodes, A 920 a and B 920 b, were seen by the three nodeshaving known locations (master nodes M1-M3 910 a-910 c). Based upon thecaptured information, the locations of ID node A 920 a and ID node B 920b are calculated.

Chaining Triangulation

In another embodiment, a node with an inferred location may be used withtriangulation techniques to determine a location of another node in awireless node network. FIG. 16 is a diagram illustrating an exemplarylocation determination through chaining triangulation in accordance withan embodiment of the invention. The locations of ID nodes A 920 a and B920 c have been determined by triangulating across master nodes M1-M3,as illustrated in the exemplary embodiment shown in FIG. 15. However, asillustrated in FIG. 16, the location of ID node C 920 c may also bedetermined according to an embodiment.

For example, an exemplary method of determining a node's locationthrough chaining triangulation begins with determining the calculatedlocation of ID node B 920 b (as explained with reference to FIG. 15).Next, a node closer to ID node B 920 b may be used to get the missingthird signal point needed for triangulation. This may be accomplished byplacing ID node B 920 b in a query (scan) mode such that it listens fora message from ID node C 902 c. ID node C is instructed to advertise,thus providing a signal that may be captured by ID node B. Aftercapturing the signal profile of C, ID node B may communicate or sharethe captured information and forward it along to the backend server 100through either of the master nodes M1 or M2. The resulting locationdetermination of ID node C 920 c may have a higher level of positionerror due to it being partially based on a calculated reference (e.g.,the location of ID node B), but the leveraged location determination ofID node C 920 c may be sufficiently accurate (or be an actionablelocation) that useful information may be gleaned about ID node C 920 c.For example, a leveraged or chained location determination of ID node Cmay indicate, with the help of context data, that nodes M1, M2, and IDnode B are all close enough to ID node C that ID node C is determined tobe within the same container nodes M1, M2, and ID node B.

Location Through Proximity to Triangulation (LP2T)

In an embodiment where chaining triangulation may determine locationthrough proximity to triangulation (LP2T), a starting point may bedetermining the relative location of an ID node to a master node basedon the proximity method, as explained above. However, when the relativelocation of the ID node has been determined, a more accurate or refinedlocation of the ID node may be determined based upon the location of allmaster nodes that can capture the RF output signal broadcast from the IDnode, and then triangulating based on observed signal strength of the IDnode. In this example, the proximity-based location is used as an inputin the triangulation calculation to estimate likely signal deteriorationhistorically observed between a node at the proximity-determinedlocation and scanning master nodes. In a further embodiment, by takinginto account historic data on patterns of signal deterioration, a moreaccurate triangulation may be possible, leading to a more accuratelocation determination.

FIG. 33 is a flow diagram illustrating an exemplary method fordetermining a node location using chaining triangulation for one of aplurality of nodes in a wireless node network having a server inaccordance with an embodiment of the invention. Such an exemplary nodelocation need not be precise or exacting, but can be sufficientlyaccurate without absolutes.

Referring now to FIG. 33, method 3300 begins at step 3305 with theserver receiving a location of a first of the nodes from the first node.Next, at step 3310, the server receives a location of a second of thenodes from the second node. For example, with reference to the exampleshown in FIG. 16, master nodes M1 910 a and M2 910 b may transmit theirrespective location coordinates from their respective onboard locationcircuitry to the server so that the server has the current locations ofthese two master nodes.

At step 3315, the server infers a location of a third of the nodes. Forinstance, in the example illustrated in FIG. 16, the server may inferthe location of ID node B 920 b. In one embodiment, inferring maycomprise having the server determine a proximate-based location of thethird node relative to another of the nodes having a known location,such that the proximate-based location operates as the inferred locationof the third node.

In another embodiment, inferring the location of the third node maycomprise having the server determine a relative location of the thirdnode to the first node (as the node having a known location) or to thesecond node (as another node having a known location). Method 3300 mayalso, in another embodiment, include having the server adjust theinferred location of the third node to determine a refined location ofthe third node based upon third node context data related to theinferred location of the third node

At step 3320, method 3300 concludes with the server triangulating thelocation of the one node based upon determined distances to each of thefirst and second nodes, and a determined distance of the one node to theinferred location of the third nodes.

In a more detailed embodiment, method 3300 may triangulate the locationof the one node by accessing first node context data related to acontextual environment near the first node and second node context datarelated a contextual environment near the second node. Such contextualenvironments may include an environment of being on a conveyor system,or within a particular facility, or next to materials that may degradeor shield signals being received by the one node. Next, the moredetailed triangulating may have the server adjust the determineddistance of the one node to the location of the first node based uponthe first node context data to provide a refined distance of the onenode to the location of the of the first node. Then, the server maytriangulate the location of the one node based upon the adjusteddetermined distance of the one node to the location of the first node,the adjusted determined distance of the one node to the location ofsecond node, and a determined distance of the one node to the refinedlocation of the third node.

In a further embodiment, method 3300 may also have the servertransmitting an instruction so as to cause the server to transmit aninstruction to cause the one node to broadcast a plurality ofadvertising signals over a period of time. In such an embodiment, thedetermined distance of the one node to the location of the first nodemay be based upon captured signals from the one node by the first nodeover the period of time and reported to the server by the first node. Inanother embodiment, the determined distance of the one node to thelocation of the second node may be based upon captured signals from theone node by the second node and reported to the server by the secondnode.

In still another embodiment, the server may transmit an instruction tocause the one node to broadcast a plurality of advertising signals atdifferent power levels. In such an embodiment, the determined distanceof the one node to the location of the first node may be based uponcaptured signals from the one node by the first node and reported to theserver by the first node. In another embodiment, the determined distanceof the one node to the location of the second node may be based uponcaptured signals from the one node by the second node and reported tothe server by the second node.

In yet another embodiment, method 3300 may also have the servertransmitting the location information out to a requesting entity (e.g.,another node, a user access device, etc.) upon receipt of a request fora location of the one node from that entity.

Those skilled in the art will appreciate that method 3300 as disclosedand explained above in various embodiments may be implemented on aserver (such as exemplary server 100 as illustrated in FIG. 5) runningone or more parts of a control and management code (such as an code 525)to implement any of the above described functionality. Such code may bestored on a non-transitory computer-readable medium (such as memorystorage 515 in an exemplary server). Thus, when executing such code, aprocessing unit of the server (such as unit 500) may be operative toperform operations or steps from the exemplary methods disclosed above,including method 3300 and variations of that method.

A server apparatus is also described in an embodiment for determining alocation using chaining triangulation for one of a plurality of nodes ina wireless node network. The server apparatus generally comprises aserver processing unit, a server volatile memory, a server memorystorage, and a communication interface. The server volatile memory,server memory storage, and communication interface are each configuredin the apparatus as coupled to the server processing unit. The servermemory storage maintains at least a program code section and locationdata related to nodes in the network. In some embodiments, the servermemory storage may also maintain context data, such as first nodecontext data and second node context data. The communication interfaceprovides a communication path operatively coupling the server with nodesin the network, such as a first and second node.

The server processing unit, when executing at least the program codesection resident in the server volatile memory, is operative to performvarious functions, such as the functions described in the steps aboverelated to method 3300. In particular, the server processing unit isoperative to receive a request over the communication interface for thelocation of the one node. Based on the request, the server processingunit is then operative to receive the respective locations of the firstand second nodes, and store the locations as part of the location datakept on the server memory storage. The server processing unit is furtheroperative to infer a location of a third of the nodes, and store theinferred location of the third node as part of the location data kept onthe server memory storage. The server processing unit then is operativeto triangulate the location of the one node based upon a determineddistance of the one node to the location of the first node, a determineddistance of the one node to the location of second node, and adetermined distance of the one node to the inferred location of thethird node. And finally, the server processing unit is operative totransmit the location information to the requesting entity over thecommunication interface in response to the request.

In one embodiment, the server processing unit may be further operativeto infer the location of the third of the nodes by being operative todetermine a proximate-based location of the third node relative toanother of the nodes having a known location, where the proximate-basedlocation operates as the inferred location of the third node.

In another embodiment, the server processing unit may be furtheroperative to transmit an instruction over the communication interface tocause the one node to broadcast a plurality of advertising signals overa period of time. In this embodiment, the determined distance of the onenode to the location of the first node may be based upon capturedsignals from the one node by the first node over the period of time andreported to the server by the first node. Alternatively, the determineddistance of the one node to the location of the second node may be basedupon captured signals from the one node by the second node and reportedto the server by the second node.

In another embodiment, the server processing unit may be furtheroperative to transmit an instruction over the communication interface tocause the one node to broadcast a plurality of advertising signals atdifferent power levels. In such an embodiment, the determined distanceof the one node to the location of the first node may be based uponcaptured signals from the one node by the first node and reported to theserver by the first node. Alternatively, the determined distance of theone node to the location of the second node may be based upon capturedsignals from the one node by the second node and reported to the serverby the second node.

In yet another embodiment, the server processing unit may be furtheroperative to infer the location of the third node by being operative todetermine a relative location of the third node to the first node or,alternatively, to the second node.

In still another embodiment, context data may be relied upon to refinelocations. More specifically, the server processing unit may be furtheroperative to adjust the inferred location of the third node to determinea refined location of the third node based upon third node context datarelated to the inferred location of the third node.

In a more detailed embodiment, the server memory storage may furthermaintains context data, and the server processing unit may be furtheroperative to triangulate by being operative to access first node contextdata as part of the context data maintained on the server memorystorage, where the first node context data is related to a contextualenvironment near the first node. Likewise, the server processing unitmay be further operative to access second node context data as part ofthe context data maintained on the server memory storage, where thesecond node context data is related a contextual environment near thesecond node. The server processing unit may then be operative to adjustthe determined distance of the one node to the location of the firstnode based upon the first node context data to provide a refineddistance of the one node to the location of the of the first node. Assuch, the server processing unit may be operative to triangulate thelocation of the one node based upon the adjusted determined distance ofthe one node to the location of the first node, the adjusted determineddistance of the one node to the location of second node, and adetermined distance of the one node to the refined location of the thirdnode.

Combined Methods for Determining Node Location

In light of the examples explained above for locating a node, oneskilled in the art will appreciate that a further embodiment expresslycontemplates using more than one of the above-described locationdetermination techniques when determining a refined location of a nodein a wireless node network. For example, such combination embodimentsmay apply an ordered or prioritized approach whereby a first locationtechnique is applied to generate first location information regardingthe location of a node in the wireless network. Thereafter, a secondlocation technique may be selected from a hierarchy or prioritized setof techniques (some of which may work better in certain circumstancesand be chosen or dynamically prioritized based upon the contextualenvironment), and applied to generate second location informationregarding the location of the node or refining the location of the node.Other embodiments may apply additional location techniques to generatefurther refined location information.

In an embodiment, the information in the exemplary hierarchy generallyidentifies which technique may be preferred to be used initially as wellas a ranked grouping or listing of when to apply other locationtechniques. Such information in the exemplary hierarchy may be fixed(based upon successful historic data and experience) or be dynamicallyaltered over time as nodes may move relative to each other and, forexample, based upon context data that provides more information relativeto the a current or anticipated contextual environment.

Applying Node Location Determination in a Vehicular Environment

The various exemplary methods and techniques described above fordetermining the location of a node provide an advantageous way to locatea node. However, further embodiments may advantageously apply suchmethods and techniques in a vehicular environment when dealing withlogistics operations where a node is to be located in a vehicle, movedwithin a vehicle, or removed for delivery from a vehicle.

Essentially, embodiments may use a package enabled with a node(generally referred to as a node package or node-enabled package) toship one or more items and such a node package may be advantageouslyplaced, located, moved, or removed for delivery in avehicle/transportation/shipping/logistics environment. As explainedthroughout this description, a node package is generally a package to beshipped that is related to a particular node. The node and the relatedpackage travel together as part of the shipping process. In a generalembodiment, the node may simply be within the package. In anotherembodiment, the node may be attached to the package (e.g., adhered to aninterior portion of the package, fixed to a part of the package whereone or more status indicators of the node may be visible through thepackage, etc.). In another embodiment, the node of the node package maybe part of the package or the packaging materials used to comprise anexterior, interior, or separating/cushioning material within the nodepackage. In more detail, the node may be integrated as part of thepackage or packaging materials (e.g., integrated as part of a pallet, aULD container, a corrugated fiberboard box, and the like). In stillanother detailed embodiment, the node of the node package may be fullyor partially embedded within the package or packaging materials used tohelp form a general container, which maintains an item to be shippedalong with the node.

FIG. 20 is a diagram illustrating exemplary node packages located in anexemplary vehicle environment in accordance with an embodiment of theinvention. Referring now to FIG. 20, exemplary vehicle 9300 isillustrated as an example of a general mobile logistics transport orconveyance carrying packages being shipped. Those skilled in the artwill appreciate that vehicle 9300 may be implemented as various types oflogistics conveyances (e.g., automobile, delivery van, autonomousvehicle, truck, trailer, train, aircraft, marine vessel (ship), etc.).Within exemplary vehicle 9300, packages may be placed, stored, andorganized within different storage devices or units, such as storageunit A 9305 or storage unit B 9310. In general, a storage device or unithelps to maintain one or more packages in a configuration that helps toassure save shipment, minimize damage to the packages, and provide a wayto organize what is being stored. Different embodiments of a storageunit may store a single package or may storage a wide variety ofdifferent types of packages that use different types of packagingmaterials (e.g., corrugated fiberboard boxes, wooden and non-woodenpallets, containers, etc.) and in large numbers.

Vehicle 9300 includes a vehicle master node 9315—an exemplaryimplementation of a master node, such as master node 110 a shown anddescribed with respect to FIG. 4. Vehicle master node 9315 is shownoperative to communicate with server 100 over a longer-rangecommunication interfaces (such as interface 485 on exemplary master node110 a) and operative to communicate with other nodes, such as masternode 9320 associated with storage unit A 9305, master node 9325associated with storage unit B 9310, and other nodes associated withparts of such storage units and node packages stored within the storageunits. In more detail, each storage unit may include, in someembodiments, built-in nodes associated with particular shelves, lockers,receptacles, or other parts of the particular storage unit.

Thus, an exemplary storage unit (such as storage unit A 9305) may be anode-enabled storage unit used within a logistics vehicle to safely andintelligently transport node packages. As such, the exemplary storageunit may itself have a hierarchy of nodes (e.g., a master node, and oneor more other nodes (ID nodes or other master nodes) assigned todifferent parts of the unit) and be operative to detect the location ofparticular node packages via the various location determination methodsdiscussed herein as the node package is placed in a storage locationwithin the unit, moved between storage locations of the unit or betweendifferent units, or simply removed from the storage location within theunit.

As shown in FIG. 20, various node packages 9330 a-9330 d may be kept indifferent storage locations of storage unit A 9305 within vehicle 9300.Similarly, other node packages 9330 e-9330 g are kept in portions ofstorage unit B 9310. Such node packages may be placed into particularstorage locations according to shipping information related to the nodepackages. For example, the node packages may be placed into particularstorage locations according to weights of the particular node packages,a planned loading scheme (such as according to an anticipated deliveryschedule), to storage capacity of the particular different locationswithin the storage unit, or according to a storage type for theparticular different locations (e.g., one location for storing envelopetypes of packages, another location for storing boxed container type ofpackages, another location for storing containerized packages (e.g.,ULDs), etc.).

Shipping of containerized groups of packages (e.g., ULD types ofcontainers made to optimize airborne logistics handling of packages) isan example of where a mobile storage unit (such as a movable unit loaddevice (ULD)) may be deployed when shipping node packages in an airborneenvironment. FIG. 21 is a diagram illustrating exemplary mobile storageunits, such as ULDs, used as containers that help ship node packages inan exemplary airborne environment in accordance with an embodiment ofthe invention. Referring now to FIG. 21, a cut-away perspective view ofan exemplary aircraft fuselage 9400 is illustrated. In particular, anexemplary floor 9405 of a cargo storage area within fuselage 9400 isshown having multiple roller elements that help facilitate movement ofcargo within the cargo area. Additionally, while not shown in FIG. 21,the cargo storage area and floor 9405 typically include structure andfastening points to help hold any cargo loaded within fuselage 9400. Thecargo storage area within exemplary fuselage 9400 may be split into anupper area and a lower area by an additional floor 9410.

The cut-away perspective example illustrated in FIG. 21 shows a lowercargo area where various ULD containers 9420 a-9420 d are shown alongwith an airborne master node 9415, which is (depending on the aircraft'slocation and communication mode and status) operative to communicatewith server 100—much like vehicle master node 9315 does as shown in FIG.20. In general, the illustrated configuration of ULD containers 9420 a-dis used similar to the storage units illustrated and described in FIG.20. For example, each ULD container 9420 a-d may have different storagelocations within it and one or more master nodes (not shown) dedicatedand attached internally so that they may track, monitor, and communicatewith different node packages loaded within the ULD as well as othernodes and a server—much like the master node 9320 for storage unit A9305 can track, monitor, and communicate with different node packagesloaded within the storage unit as well as other nodes and server 100.Node packages within each ULD may communicate with nodes in the ULD andmay communicate directly with airborne master node 9415 directly (orindirectly through other master nodes within the ULD). And as such,shipping information may be used when the node packages are placed intoparticular storage locations within a particular ULD according toweights of the particular node packages, a planned loading scheme forthe ULDs (such as according to an anticipated delivery schedule), tostorage capacity of the particular different locations within the ULD,or according to a storage type for the particular different locations.

In light of the exemplary vehicular environments shown in FIGS. 93 and94 showing structure used when initially placing, storing, maintaining,locating, moving, and eventually removing a node package for delivery,those skilled in the art will appreciate that each of the embodimentsdescribed above related to methods for locating a node may be furtherenhanced when applied to an exemplary vehicular environment. Forexample, in one embodiment, determining a node's location may furthercomprise determining a location of the node-enabled package within avehicle to be the location of the node. In a more detailed embodiment,the method that determines a node location may further generate alocation message regarding where the node-enabled package is locatedwithin the vehicle based upon the determined location of the node. Sucha message may be displayed to a user (e.g., logistics personnel thathandle packages being shipped) on a user interface of a node or useraccess device operating as a node (e.g., smartphone or smart wearabledevice). For example, such a displayed message may be a type of aninformed prompt (“Pickup Package X at Storage Location 01 in StorageUnit A”) or strategic instruction (“Place Package X in Storage Location01 in Storage Unit A”) or (“Move Package X at Storage Location 01 inStorage Unit A to Storage Location 03 in Storage Unit B”). In someembodiments, the network device or node that determines the node'slocation may also provide such a display to the user, but in otherembodiments, the location message may be transmitted to another node fordisplay to the user.

In another embodiment, an exemplary method that determines a node'slocation may also access shipping information related to thenode-enabled package and generate a relocation message regarding wherethe node-enabled package may be relocated within the vehicle based uponthe determined location of the node and the accessed shippinginformation. Such a message may be displayed to a user similar to thelocation message described above—namely, that such a relocation messagemay be displayed to a user (e.g., logistics personnel that handlepackages being shipped) on a user interface of a node or user accessdevice operating as a node (e.g., smartphone or smart wearable device)and that in some embodiments, the network device or node that determinesthe node's location may provide such a display to the user, but in otherembodiments, the relocation message may be transmitted to another nodefor display to the user.

In more detail, the shipping information may comprise weight informationon the node-enabled package that is used in determining where torelocate or initially place the node-enabled package. In anotherembodiment, such shipping information may be used to create a loadingscheme to help organize where to locate or relocate the node-enabledpackages. Thus, the location or relocation of the node-enabled packagewithin the vehicle may be determined according to a loading scheme. Inmore detail, such a loading scheme may be related to an anticipateddelivery schedule, where the node-enabled package may be placed withinor removed from the vehicle according to the anticipated deliveryschedule.

Logistics Applications of a Wireless Node Network

As described above, an exemplary wireless node network may be useful ina logistics application where an item is to be located. Further, such anexemplary wireless node network may also be useful in logisticsapplications where the item is moving between locations, and the networkprovides an enhanced level of visibility and management of the itemwithin such a logistics environment. In other words, an embodiment of anexemplary wireless node network in accordance with one or moreprinciples of the present invention helps enable enhanced logisticaloperations that manage information when shipping and tracking an itemand when the item is being delivered. FIG. 17 is a diagram illustratingan example logistics operation using exemplary components of a wirelessnode network in accordance with an embodiment of the invention.

Logistics Beyond Pickup and Delivery

Referring now to FIG. 17, an ID node 120 a is illustrated as beingdeployed and associated with an item (e.g., package 130) to be shipped.As the package 130 is being prepared for shipping 1700, and is intransit as part of shipment 1705, and is in the possession of theintended recipient 1710, components of an exemplary wireless nodenetwork are deployed to manage information regarding the shipment duringthese three phases.

In a general example of using a wireless node network for managinglogistics related to an item to be shipped, a shipping customer mayinitially register the item (such as package 130) with a node (such asan ID node) to be shipped from an origin location to a destinationlocation. One or more management hand-offs of the item and node occursas the item and the ID node collectively transit a path from the originto the destination. Each hand-off may be based upon an awareness of theshipment path the ID node associated with package 130 will take as it istransferred through a shipping path from its origin to destination.Hand-off of the package 130 and ID node are managed and coordinated withmaster nodes (such as master nodes 110 a-110 h), which are managed byserver 100, along the anticipated shipment path. During operation alongthe shipping path, server 100 receives information and updates fromnodes, manages and authorizes hand-offs between different nodes, andtracks information related to current associations, shared data, sensordata available, locations of the nodes, and context data that helps torefine the location of nodes. Thus, with the ID node associated withpackage 130, the visibility of the package 130 may be extended for thecustomer beyond the conventional custodial control during transit 1705as the shipping customer prepares the item for shipment 1700 prior to aninitial drop-off and after delivery of the item to the recipient 1710.

In a more detailed embodiment, an exemplary method for managinglogistics related to an item to be shipped using a wireless node networkbegins with registering a node with the item to be shipped. For example,the shipping customer may control user access device 200, and use device200 to initially associate an ID node 120 a and package 130 with atracking number as part of preparing to ship the package 130 (a type ofitem). In one embodiment, device 200 may use a particular app or otherprogram module resident and operating on device 200 to input thetracking number of the package 130. Device 200 then provides thatinformation back to server 100 via network 105 to associate the trackingnumber with the package 130 and ID node 120 a. Device 200, in someembodiments, may then print a label for the shipment of package 130 (andID node 120 a). In another embodiment, ID node 120 a may be apreprogrammed node with pre-existing shipping and payment relatedinformation associated with it. Further details of a label-less shippingand payment in another embodiment are described below.

Concurrent with this action, the shipping customer may associate ID node120 a with package 130. For example, the shipping customer may place theID node 120 a within package 130 and, in some cases, physically attachthe ID node 120 a to a particular part of package 130. In anotherexample, the shipping customer may place an exterior label on package130 where the label itself includes ID node 120 a. Other examples mayeffectively group ID node 120 a with package 130 within a largerpackage, container, or pallet of items or packages that collectivelytravel together.

In this manner, device 200 may operate as a type of master node undercontrol of the app or other program module, and be associated with thepackage 130 and ID node 120 a from an association managementperspective. For example, device 200 may operate via the app or otherprogram module along with Bluetooth® hardware and software working ondevice 200 to communicate with ID node 120 a. Other embodiments may relyon other short-range communication interfaces for device 200 tocommunicate with ID node 120 a. And in one embodiment, device 200 mayreceive one or more security credentials from server 100 in order toconnect and actively pair or connect with ID node 120 a.

With at least the shipping information at the server 100, server 100 maydetermine a predicted shipping path for the package 130. In oneembodiment, server 100 may have historic data indicating an optimalroute for shipping an item from point A to point B that uses aparticular shipping path (e.g., pick-up near A by a particular courier,transport by vehicle to a particular facility, further transport viaaircraft to another facility near point B, and transport by vehicle tofacilitate delivery by a courier at point B). In one example, thepredicted path may only be for a portion of the route between twopoints, such as an origin point and a destination point.

In a further example, the predicted path (or part thereof) may beadjusted based on the contextual environment of an item being shipped.For instance, depending on context data (such as weather information,historic data on success for particular transit segments, capacityinformation for third party carriers, etc.), server 100 may alter theinitially predicted shipping path to provide a refined predictedshipping path that is more optimized under the current conditions andcontext. This allows the server 100 to further anticipate which masternodes may be used along an anticipated shipping path (or refinedshipping path), to help efficiently manage shipment of the package 130to point B. Those skilled in the art will further appreciate that anembodiment may only partially identify what master nodes may be usedalong the anticipated shipping path (or refined shipping path), and thatfurther master nodes may be identified as the package 130 is actively inroute to point B depending on context data (e.g., master nodeavailability, weather information, etc.).

In a more detailed example, server 100 may use sort data analytics topredict an appropriate shipping path along which the package 130 and theID node 120 a will travel, identifying predicted master nodes the IDnode 120 a will be within range of during its journey. In the exampleflow illustrated in FIG. 17, nodes 110 a-110 h refer to different masternodes along an exemplary predicted shipping path, which includes atleast a pick-up and drop-off of ID node 120 a and package 130 at anorigin and destination, respectively.

In one example, the shipping customer may place package 130 and itsassociated ID node 120 a in a drop box or repository for items to beshipped. In the illustrated example of FIG. 17, drop box is representedas drop node 110 a. Essentially, drop node 110 a may be implemented witha type of master node connected to or integrated into a drop box orlocker unit type of logistics repository (more generally referred toherein as a node-enabled logistics receptacle). As the shipping customerphysically places ID node 120 a into drop node 110 a, device 200 mayhand-off ID node 120 a to drop node 110 a, update server 100 with thisassociation information, and disassociate from ID node 120 a. In thismanner, the system has visibility into the status and location of anitem (such as package 130) prior to pick-up from drop node 110 a.Further details of an exemplary node-enabled logistics receptacle aredescribed below.

At the drop node 110 a, a courier may pick-up the package 130 and IDnode 120 a. The courier has a courier node 110 b, which knows thetracking number and associated ID node 120 a at time of pickup, or looksup the ID node 120 a MAC address based on a captured tracking number(part of information broadcast or advertised by ID node 110 a.Basically, the master node responsibility transfers to or is otherwisehanded off to courier node 110 b, which now acts as a master nodeactively connected and associated with ID node 120 a (by virtue ofcommunications from courier node 110 b back to server that authorizesthe association of ID node 110 a with courier node 110 b anddisassociates drop node 110 a with ID node 110 a).

Similar handoffs occur between different master nodes and ID node 120 aoccur as package 130 and ID node 120 a transit the anticipated shippingpath in accordance with instructions sent to different master nodes byserver 100. In one embodiment, associations are accomplished during suchhandoffs with security credentials requested, authorized, andtransmitted to the appropriate master node. In another embodiment,associations are merely passive associations that do not require activeand authorized pairings. Yet, the passive association still may allowthe system to keep track of ID node 120 a and package 130 as theytransit the anticipated shipping path.

New associations (active and passive) and disassociations are updated toserver 100. And server 100 may change programming in different nodes aspackage 130 and ID node 120 a transit the shipping path—such as changingthe operation of a master node (such as ULD node 110 e) to shift tooperating as an ID node while airborne or when GPS signals are lost. Inanother example, certain mobile types of node may have responsibilitieschanged to wired types of nodes as a way of preserving the power of amobile type of node. If ID node 120 a fails to associate for a certaininterval and needs to be reacquired, ID node 120 a may update its statusflag to a particular Alert Stage and may attempt to communicate with anincreasingly broader range of master nodes in order to be found.

During the transit, server 100 may share information with differentnodes, such as context data, timer/clock data, environmental data, etc.Sensor data from the ID node 120 a may be gathered via scans from amaster node, and then forwarded back to server 100. And as server 100manages the associations, handoffs, and information going to and comingfrom ID node 120 a (via master nodes), server 100 is able to determinethe location of ID node 120 a using one or more of the various locationdetermination techniques described above. As such, server 100 is able toprovide information related to the ID node 120 a and its related package130 in response to requests for such information.

When package 130 and ID node 120 a arrive at the destination (e.g.,point B), courier node 110 h may update server 100 once ID node 120 a isplaced at the destination and disassociated with courier node 110 h.However, visibility need not end at such a drop-off event (such asarriving at the destination). The recipient customer's user accessdevice 205 may act as another master node, and associate with ID node120 a after delivery. In one example, server 100 is notified by couriernode 110 h that delivery has been made. Thereafter, server 100 maynotify device 205 with this information. In response, an app or otherprogram module on device 205 may cause device 205 to operate as a nodeand to actively seek association with ID node 120 a. When device 205 andID node 120 a connect and are given authorization by server 100 toactively associate, server 100 is notified and may provide furtherinformation to device 205 (e.g., sensor data, etc.) and may be able todetermined updated location data about ID node 120 a and package 130after delivery has occurred. In another example, active association maynot be needed between device 205 and ID node 120 a as status informationmay still be gathered by device 205 via passive association, where thestatus information provides further visibility regarding the ID node 120after delivery to the destination.

FIGS. 18 and 19 are flow diagrams illustrating various exemplary methodsfor managing a shipment of an item using a wireless node network, suchas that illustrated in FIG. 17. Referring now to FIG. 18, exemplarymethod 1800 begins by transmitting shipping information to the server toregister the ID node and the item to be shipped at step 1805 andassociating the ID node to a first master node related to a predictedpath for shipping the item at step 1810. At step 1815, the server isupdated to reflect the association between the ID node and the firstmaster node. Typically, this may come in the form or a communicationfrom the first master node to the server. When the first master node isa user access device (e.g., one of a laptop computer, a desktopcomputer, a tablet device, a personal area network device, a smartphonedevice, and a smart wearable device) that is operated by a shippingcustomer, the server may be updated to become aware that the ID node isassociated with the first master node prior to a pick-up event in thepredicted path.

For example, a shipping customer may use their smartphone to entershipping information and register that the ID node and the item (such aspackage 130) are to be shipped from an origin point to a destinationpoint. Prior to when the item and ID node are picked up by an initialcourier (e.g., from a drop box, locker unit, or other receptacle), theshipping customer's smartphone operates as the first master node and isassociated with the ID node. As such, and with an update to the server,the server now has visibility into the status and location of the IDnode prior to a pick-up event in the predicted shipping path from theorigin point to the destination point.

The method 1800 may continue at step 1820 by disassociating the ID nodeand the first master node when associating the ID node and a secondmaster node related to the predicted path as the ID node transits thepredicted path. In one example, the ID node need not disassociate withthe first master node commensurate with associating with the secondmaster node. Thus, those skilled in the art will appreciate that the IDnode may be associated with one or more master nodes at a given point intime and may be selectively disassociated with certain master nodesdepending on the need for the ID node to securely share data withdifferent master nodes.

At step 1825, the server is updated to reflect the disassociationbetween the ID node and the first master node (if that has occurred yet)and the association between the ID node and the second master node asthe ID node continues to transit the predicted path. At step 1830, themethod may associate the ID node to a third master node near an end ofthe predicted path for shipping the item, and then at step 1835 notifiesthe server to reflect the association between the ID node and the thirdmaster node.

In the method 1800, associating the ID node to the third master node instep 1830 may be performed after a drop-off event in the predicted path.The method may also rely upon context data to adjust for anenvironmental aspect of the predicted path when associating the ID nodeto any of the first, second, or third master nodes.

For example, after the item and ID node are delivered to or near thedestination, the recipient's smartphone may operate as the third masternode associated with the ID node. Data, such as sensor data, may beshared with the recipient while the recipient's smartphone operates asthe third master node associated with the ID node. As such, and with anupdate to the server, the server now has visibility into the status andlocation of the ID node after a drop-off event.

Thereafter, the recipient may unregister the ID node and item given theitem is now in the recipient's possession and control. For example, therecipient may remove the ID node from the item (e.g., the package 130),deactivate the ID node to otherwise power down the device, update theserver regarding the deactivated status of the ID node (and thedisassociation of ID node and the third master node), and then clean upand/or recharge the ID node for future use in shipping another item.

Method 1800 may also include receiving context data related to thepredicted path. In one embodiment, such context data may advantageouslyallow for adjustments due to one or more environmental aspects of thepredicted path when associating the ID node to any of the master nodes.For example, the context data may include scan data indicating the typeof material in package 130 (the item), which may cause RF shieldingissues with the ID node.

Referring now to FIG. 19, exemplary method 1900 is explained from theperspective of the server, which can authorize certain types of nodeassociations. The server may be updated, in some embodiments, withassociation information when an ID node and a master node are passivelyassociated. In such a situation, the nodes have not established anauthorized association where they can securely share data. However, asmethod 1900 explains in more detail, an embodiment may manage a shipmentof an item when active associations are established.

Method 1900 begins with the server receiving shipping information toregister the ID node and the item to be shipped in step 1905. The method1900 then provides a first set of authentication credentials (e.g.,security pin information) to a first master node to permit the ID nodeto associate with the first master node related to a predicted path forshipping the item at step 1910. In one example, the first master nodemay be a user access device, such as a laptop computer, a desktopcomputer, a tablet device, a personal area network device, a smartphonedevice, or a smart wearable device. And step 1920 may be performed priorto a pick-up even in the predicted path.

At step 1915, the server receives an update to reflect the associationbetween the ID node and the first master node. The method 1900 thenprovides a second set of authentication credentials to a second masternode to permit the ID node to associate with the second master node anddisassociate the ID node from the first master node as the ID nodetransits the predicted path at step 1920. At step 1925, the server thenreceives an update to reflect the association between the ID node andthe second master node as the ID node continues to transit the predictedpath (or a portion of a predicted path). When the ID node and the firstmaster node disassociate, the server may also be updated.

In some examples, the method 1900 may have the server provide a thirdset of authentication credentials to a third master node to permit theID node to associate with the third master node as the ID node reachesan end of the predicted path for shipping the item at step 1930. In someexamples, this step may be performed after a drop-off event in thepredicted path.

Finally, at step 1935, the server receives a notification that reflectsthe association between the ID node and the third master node. When theID node and the second master node disassociate, the server may also beupdated.

In method 1900, another embodiment has the server providing any of themaster nodes with context data related to an environmental aspect of apart of the predicted path. For example, exemplary context data mayinclude layout data related to a facility in which the ID node is movingbetween master nodes. In more detail, the received context data may berelied upon to adjust for an environmental aspect of the predicted pathwhen associating the ID node to any of the first, second, or thirdmaster nodes.

In still another embodiment, method 1900 may also determining a locationof the ID node based upon association information received by the serverand location information related to at least one of the first, second,or third master nodes.

As previously discussed, the server may predict a transit route from afirst point to a second point along at least a portion of the predictedpath for shipping the item. In one example, the first point is an originand the second point is a destination point with both being identifiedin the shipping information of the item. However in other examples, thefirst and second point along a predicted path may merely be interimpoints without encompassing the originating shipment point or theultimate destination of the item being shipped. Further, another examplemay adjust the predicted path as the ID node transits the path. In thisway, the server may adapt based upon, for example, context data, so asto optimize or at least account for a changing contextual environmentwhen managing the shipment of an item.

In another embodiment, a non-transitory computer-readable medium isdisclosed that contains instructions, which when executed on a processor(e.g., processor 500 of server 100), performs another embodiment of amethod for managing a shipment of an item using a wireless node networkhaving at least one ID node, a plurality of master nodes, and a server.In this embodiment, the exemplary method begins with the serverreceiving shipping information to register the ID node and the item tobe shipped. The method predicting a first portion of a transit route forthe item from a first point to a second point. For example, a firstpoint may be the origin point and the second point may be thedestination point—both of which are identified in the shippinginformation. In another example, the first and second points are any twopoints along the transit route. Furthermore, the transit route may bepredicted as a series of portions or segments that may use particulartypes of master nodes during transit (e.g., master nodes used by aparticular courier for pick-up, an anticipated vehicle used by thepickup courier, one or more anticipated facilities that may be used bythe vehicle, an anticipated air route (e.g., an anticipated departingairport, an anticipated aircraft, anticipated types of containers suchas a type of ULD or pallet used on the aircraft, and an anticipatedarriving airport), a facility near the anticipated arriving airport, avehicle used to carry the item, and a courier that may deliver the itemat the destination point). Those skilled in the art will realized thatsome of the potential portions of an exemplary predicted path or transitroute may be relatively simple for a local delivery, or may be quitecomplex from an intermodal perspective when the origin point anddestination points are very far away from each other.

Next, the method authorizes a first master node to associate or connectwith the ID node near the origin point. This may be done prior to apick-up event for the ID node and item being shipped. For example, whenthe first master node is a user access device (e.g., a laptop computer,a desktop computer, a tablet device, a personal area network device, asmartphone device, and a smart wearable device) for the shippingcustomer, visibility as to the status and location of the ID node may beextended to prior to a pick-up event. In one embodiment, such anauthorization is performed by the server 100 when it receivesinformation from the first master node regarding the ID node, determinesthat the first master node and the ID node should be actively paired andassociated, and the server 100 sends the appropriate security pininformation as a type of authorization credentials that permit the firstmaster node to actively pair and connect with the ID node. After thefirst master node is associated with the ID node, the server receives anupdate reflecting the association.

Next, the server may authorize a second master node to associate withthe ID node as management responsibility of the ID node is handed offfrom the first master node to the second master node at the second pointon the predicted transit route. In one embodiment, the method mayauthorize the first master node to disassociate with the ID node.However, in other embodiments, the first master node may stay associatedwith the ID node—even after the ID node is authorized to associate withthe second master node. The server then receives an update to reflectthe association between the ID node and the second master node as the IDnode continues on the predicted first portion of the transit route.

The method may further authorize the second master node to disassociatewith the ID node and a third master node to associate with the ID nodeas management responsibility of the ID node is handed off from thesecond master node to the third master node near the destination pointon the predicted transit route. This may be done prior to a pick-upevent for the ID node and item being shipped. For example, when thethird master node is a user access device (e.g., a laptop computer, adesktop computer, a tablet device, a personal area network device, asmartphone device, and a smart wearable device) for the recipient,visibility as to the status and location of the ID node may be extendedto after a drop-off event. After the third master node is associatedwith the ID node, the server receives a notification to reflect theassociation between the ID node and the third master node.

And during the method, the server may determine a location of the IDnode based upon association information received by the server andlocation information related to at least one of the first, second, orthird master nodes. As discussed above, various techniques are availablefor locating a node and, in some cases, adjusting for adverse RFenvironmental conditions with context data to more accurately refine thelocation of a node. As such, the server keeps track of the location ofnodes in the wireless node network, and may provide that information (aswell as other types of shared or sensor information) when requested andauthorized to do so.

From a system perspective of such a logistics application of a wirelessnode network, an exemplary system is disclosed for managing a shipmentof an item using a wireless node network. With reference to FIG. 17, theexemplary system generally comprises an ID node (such as node 120 a), aplurality of master nodes (such as nodes 110 a-110 h), and a server(such as server 100). The ID node is registered to the item (such aspackage 130) being shipped. Each of the master nodes are predicted to belocated at a different part of an anticipated transit route for the itemas the item is shipped from an origin point to a designation point ofthe anticipated transit route. Each of the master nodes is operative tocommunicate with the ID node over a short-range communication path, andoperative to communicate with other master nodes and the server 100.

The server operates to track and report a location of the ID node and alocation of the master nodes. As shown in FIG. 17, server 100 relies onnetwork 105 to communicate with different master nodes (110 a-110 h) aswell as user access devices 200, 205 that may operate and function as amaster node associated with ID node 120 a at certain times. Aspreviously discussed, server 100 may employ a variety of differenttechniques (or a combination of different techniques) for determiningthe location of ID node 120 a or one of the other nodes in the network.

The server is also operative to facilitate the transfer of managementresponsibility of the ID node between different master nodes as the IDnode moves along the anticipated transit route. For example, asdiscussed above, nodes communicate via broadcast and scanning methods,and may be associated under control of the server 100 as part ofmanaging the wireless node network. In this way, a first of the masternodes may be associated with the ID node prior to a pick-up event forthe ID node and item to be shipped. In one example, user access device200 may operate as a master node and be associated with ID node 120 aprior to being placed into drop node 110 a and picked up by a courierfrom the receptacle related to that drop node 110 a.

Later, a second of the master nodes may be associated with the ID nodeafter the ID node is disassociated with the first of the master nodes atan intermediate point of the anticipated transit route. And, a third ofthe master nodes may be associated with the ID node after a drop-offevent for the ID node and item to be shipped. For example, user accessdevice 205 may operate as a master node and be associated with ID node120 a after the ID node 120 a and item are dropped off at an intendeddestination point (e.g., a type of drop-off event).

In an embodiment of the system, each of the master nodes may beoperative to update the server upon completing a disassociation orassociation with the ID node. This provides the server with associationinformation with which it can use to manage and track the nodes in thewireless node network. When associating nodes, the server may beoperative to transmit a set of authorization credentials to one of themaster nodes and the ID node to authorize a desired association betweenthe master node and the ID node. The server may also be operative todetermine the location of the ID node based upon context data, such asinformation relating to an environmental aspect of a part of theanticipated transit path (e.g., RF shielding aspects of the item beingshipped with the ID node or a container holding the ID node, buildinglayout information, etc.).

Those skilled in the art will readily appreciate that operations of suchan exemplary wireless node network, as set forth herein, are not limitedto tracking just a package, but may be used to manage logistics andtracking of other types of items, such as an object or a person. Indeed,some embodiments provide enhanced capabilities that facilitate bettertracking of items, objects, and people as they move to a morerestrictive indoor environment, by using a low power ID node inadvertising mode in the presence of one or more master nodes.

Enhanced Delivery & Pickup Management

In light of the above description about elements of an exemplarywireless node network and how they may be used to locate and trackitems, further embodiments may leverage one or more elements of theexemplary wireless node network to help enhance delivery/pickupmanagement of an item via, for example, selective delivery releasecontrol implemented with elements of the node network. Further, elementsof an exemplary wireless node network may also be useful in improvedlogistics applications where elements may sense an adversedelivery/pickup condition in a proactive and more timely manner thatinvolves relevant corrective delivery/pickup notifications to addressthe sensed condition (e.g., when an item has been dropped off or pickedup without meeting certain parameters, such as delivery to the intendeddestination, delivery during an intended time period, being picked up bythe right entity, etc.). Further still, elements of an exemplarywireless node network may be deployed to improve how to monitor an itemwithin an inventory not yet shipped and generate a pickup relatednotification related to an authorized status for release of the itemfrom the inventory to improve how to monitor inventory and automaticallyidentify when an item is not authorized to move from a particularlocation using such interoperating node elements. The followingembodiments that enhance and improve delivery/pickup management of anitem may be deployed and implemented using aspects discussed in moredetail above (e.g., locating nodes, node association, etc.). FIGS. 34-44help explain various embodiments that enhance and improve deliverymanagement and particularly useful and proactive delivery notificationsusing exemplary components of a wireless node network in accordance withan embodiment of the invention.

Selective Delivery Release Control

In various embodiments, an item may be maintained or stored within atype of container, receptacle, repository, or storage unit where amaster node is connected to or assembled as part of the unit (generallyreferred to as a node-enabled logistics receptacle). In general, anexemplary node-enabled logistics receptacle may temporarily maintaincustody of one or more items (along with their respective ID nodesshould one be present with a particular item). An exemplary node-enabledlogistics receptacle may have an entrance opening through which an itemmay pass (along with its related node) into a storage area of thereceptacle. Thus, the storage area maintains the item (and the relatednode if present) after it is placed within the receptacle.

Further embodiments of an exemplary node-enabled logistics receptaclemay be implemented as a secure access type of receptacle (such as alocker type of logistics receptacle) having an entrance opening that issecured with a lockable element (such as a door), as will be explainedin more detail below. As such, an item temporarily maintained with thestorage area of the receptacle may be secured with the lockable elementand released when the lockable element is unlocked.

FIG. 34 is a diagram illustrating an exemplary logistics vehicle thatoperates as a type of node-enabled logistics receptacle in accordancewith an embodiment of the invention. Referring now to FIG. 34, exemplarylogistics vehicle 3400 is illustrated as a general mobile logisticstransport or conveyance capable of transporting or carrying one or moreitem (such as a package, an object, a palletized group of packages, aperson, or piece of equipment). Those skilled in the art will appreciatethat vehicle 3400 (similar to exemplary vehicle 9300 described abovewith respect to FIG. 20) may be implemented as various types oflogistics conveyances (e.g., automobile, delivery van, autonomousvehicle, truck, trailer, train, aircraft, marine vessel (ship), etc.).

Within exemplary vehicle 3400, one or more items 3430 a-3430 d may beplaced, stored, and organized within a storage unit 3405. In someembodiments, vehicle 3400 itself may operate as storage unit 3405 thatcan maintain, store, and keep temporary custody of the items 3430 a-3430d. While exemplary vehicle 3400 is shown in FIG. 34 with a singlestorage unit 3405, those skilled in the art will appreciate that otherembodiments of vehicle 3400 may include multiple storage units (similarto that shown with exemplary vehicle 9300 in FIG. 20). In general, astorage device or unit, such as storage unit 3405 in logistics vehicle3400, effectively helps to maintain one or more items in a temporarystorage configuration (such as a confined area or in a secure captureconfiguration where the item is unable to be released from thereceptacle). Such a configuration may help to assure safe transport orshipment, minimize damage to the item stored within the unit 3405, andprovide a way to organize what is being stored within logistics vehicle3400. Different embodiments of a storage unit may store a single item(such as items 3430 a and 3430 b stored in storage areas 3415 a and 3415b, respectively), may store multiple items (such as items 3430 c and3430 d collectively stored in storage area 3415 c), or may store a widevariety of different types of items that may use different types ofpackaging materials (e.g., corrugated fiberboard boxes, wooden andnon-wooden pallets, containers, etc.) and in larger numbers than shownin FIG. 34. Thus, those skilled in the art will appreciate that whilethe logistics receptacle implemented with storage unit 3405 and vehicle3400 is a general embodiment, further embodiments may involve larger,more complex, logistics vehicles and storage units disposed within thevehicles to accommodate a desired variety of items depending on theintended use of the embodiment.

In the embodiment shown in FIG. 34, exemplary logistics vehicle 3400includes a master node 3410 for storage area 3405 (such as exemplarymaster node 110 a shown and described with respect to FIG. 4). In anembodiment where logistics vehicle 340 operates as the storage area 3405itself, master node 3410 may be considered a vehicle master node (suchas exemplary vehicle master node 9315 shown in FIG. 20). However, asshown in FIG. 34, master node 3410 is shown disposed in logisticsvehicle 3400 and operative to communicate with server 100 over alonger-range communication interfaces (such as interface 485 onexemplary master node 110 a) while also operative to communicate withother nodes, such as nodes 3420 a-3420 d respectively related to items3430 a-3430 d within storage 3405. In one embodiment, for example,server 100 may provide shipping information related to one or more ofitems 3430 a-3430 d to master node 3410 on request or as a type ofpreloading of relevant shipping information into the memory of masternode 3410. In another embodiment, one or more of nodes 3420 a-3420 d maycommunicate shipping information on their respective related item up tomaster node 3410. In this way, master node 3410 may operate withawareness of the different intended delivery locations for items 3430a-3430 d maintained within storage 3405.

Master node 3410, as associated with storage unit 3405 and disposedwithin logistics vehicle 3400 (or as the vehicle master node forlogistics vehicle 3400), may operate as part of a mobile node-enabledlogistics receptacle that can communicate with other nodes, such as adelivery location node 3440 or a mobile user access device 3445operating as a type of node in an exemplary wireless node network. Insome embodiments described in more detail below, master node 3410 mayreceive signals broadcast by delivery location node 3440 (i.e., a nodeassociated with an intended delivery location for an item) to helpverify when it is appropriate to unlock or release a particular itemfrom storage 3405. Such verification or validation may involve receivingsuch signals over a secure connection, and may involve a preauthorizedtype of validation that allows for automatic release upon detecting thesignal from node 3440 or, in other instances, may involve a promptedinterchange between node 3440 and master node 3410 as described in moredetail below.

The intended delivery location for an item may be identified as part ofshipping information. An exemplary intended delivery location mayinclude coordinates of a location, an address for a location, or alocation related to the recipient or an identified recipient nodedevice. For example, an exemplary delivery location node 3440 may be afacility master node associated with a facility mail room that is at theintended delivery location coordinates or address for an item. Inanother example, an exemplary delivery location node 3440 may be amobile master node associated with a courier (generally considered to bepersonnel involved in shipment activities related to an item), ashipping customer (generally an entity that causes the item to beshipped), or a recipient (generally an entity that is to receive theitem as a type of hand off or change in temporary custody of the item asthe item transits towards an ultimate delivery destination or the finalchange in custody of the item at the ultimate delivery destination).Thus, those skilled in the art will appreciate that delivery locationnode 3440 may be stationary/fixed and related a physical location, maybe mobile and related to a movable location, and need not be theultimate delivery destination for an item as the intended deliverylocation may essentially be considered in some embodiments as away-point location.

Similar to delivery location node 3440, a mobile user access device 3445may be operating as a node associated with the intended deliverylocation for an item in some embodiments where the location of mobileuser access device 3445 may be identified as the intended deliverylocation for an item. Thus, signals from device 3445 may be used, asexplained below in more detail, to help verify when it is appropriate tounlock or release a particular item from storage 3405. Embodiments mayhave mobile user access device 3445 associated with a customer shippingthe item or a recipient for the item (whether temporary receipt or asthe ultimate recipient of the item). As such, alerts and notificationsmay be provided to the shipping customer and recipient depending onwhether they are associated with node 3440 and/or 3445.

And similar to that described above regarding node 3440, suchverification or validation may involve receiving such signals over asecure connection, may involve a preauthorized type of validation thatallows for automatic release upon detecting the signal from mobile useraccess device 3445 or, in other instances, may involve a promptedinterchange between mobile user access device 3445 and master node 3410as described in more detail below.

FIGS. 35A-35C are diagrams illustrating an exemplary mobile node-enabledlogistics receptacle having a lockable element in exemplary stageschanging from a locked state to an open or unlocked state in order toselectively release an item from the receptacle in accordance with anembodiment of the invention.

Referring now to FIG. 35A, an embodiment of storage unit 3405 is shownwith master node 3410 as an exemplary mobile node-enabled logisticsreceptacle in a simplified manner as having a single storage area 3415a. Item 3430 a (and related ID node 3420 a) as shown been placed withinstorage area 3415 a and maintained there. As such, ID node 3420 a may beoperative to communicate with master node 3410 to, for example, provideidentification information related to item 3430 a and/or node 3420 a aswell as shipping information related to item 3430 a.

The exemplary embodiment of storage unit 3405 shown in FIG. 35A includesan exemplary lockable element 3505 that secures an entrance 3500 intostorage space 3415 a within unit 3405. In general, lockable element 3505is a release mechanism under electronic locking control, and mayinclude, for example, a door secured by a lock but may include one ormore electronically controlled grips or clasps that maintain the item ina secure configuration relative to the receptacle. In the embodimentshown in FIG. 35A, lockable element 3505 may generally be a lockabledoor, hatch, flap, or other barrier that can be secured in a position toprovide either access through entrance 3500 or to prevent access throughentrance 3500 to what is maintained within storage space 3415 a. Asshown in the embodiment illustrated in FIG. 35A, lockable opening 350 isa barrier door with a hinge 3510 pivotally coupling the opening 3505 tothe storage unit 3405. In FIG. 35A, lockable element 3505 is shown in aclosed or locked state where the side of lockable element 3505 opposinghinge 3510 is secured in place with an electronically actuated lockingelement 3515.

As shown in FIG. 35B, the electronically actuated locking element 3515is operatively coupled to master node 3410 and may be operated withsignals from master node 3410 to control access to the mobilenode-enabled logistics receptacle's storage area 3415 a (such as shownbeing disposed within vehicle 3400 in FIG. 34). As such, electronicallyactuated locking element 3515 is generally a type of actuator coupled tothe master node 3410 and the lockable element 3505. As such, exemplaryactuated locking element 3515 may receive a release signal from masternode 3410 to actuate element 3515 and change the state of the lockableelement 3505 from a closed or locked state to an open or accessiblestate. More specifically, upon receiving the release signal from masternode 3410, electronically actuated locking element 3515 caused pinelement 3520 to move to a different position, thus no longer obstructingand preventing lockable element 3505 from swinging open. Thus, asactuated to a non-obstructing position as shown in FIG. 35B, lockableelement 3505 is now in the open or accessible state and opening 3505 maybe swung open as shown in FIG. 35C to allow for selective release ofitem 3430 a from within storage area 3415 a and provide delivery accessto item 3430 a. The particular condition upon which an embodiment ofmaster node 3410 may provide the release signal is discussed in moredetail with respect to FIG. 36 below.

In general, releasing an item from the receptacle in an embodimentselectively allows the item to be transferred from the receptacle. Asshown and explained above with respect to FIGS. 35A and 35B, selectiverelease of the item from the receptacle may involve selectively andelectronically unlocking a lockable element 3500 (via an actuatedlocking element) that otherwise obstructs an entrance 3500 to where theitem is temporarily maintained. In another embodiment, selectivelyreleasing an item from the receptacle may involve a different type ofsecuring mechanism. For example, releasing an item from the receptaclemay involve causing the item to slide out from or drop from thereceptacle, causing the item to separate from the receptacle, or causingthe item to be deposited from the receptacle at a location. In otherwords, while selective release of an item from the receptacle in oneembodiment may involve simply unlocking element 3505 (e.g., unlocking adoor to a particular storage area of a mobile node-enabled receptacle)as shown in FIGS. 35A-35B, other embodiments may selective release theitem from the receptacle by having lockable element 3505 implementedwith doors that drop open below allowing the item to vertically transferor move from the receptacle with or without human intervention. Causingthe item to slide, drop, separate, or otherwise be deposited out of thereceptacle may involve releasing the appropriate securing structuredeployed as types of lockable elements (also referred to aselectronically controlled securing apparatus elements), such as one ormore articulating grips holding the item in place, one or more doorssupporting the item in place, one or more belts or straps securing theitem in place, and the like. Further, additional articulating members atthe control of master node 3410 may be considered exemplary types oflockable elements deposed within the receptacle to facilitate thetransfer (such as a tilting support surface to enable sliding out of theitem from within the receptacle, or a robotic arm operative to capturethe item and transfer the item out of the receptacle from its positionwithin the receptacle). Thus, for example, an embodiment may selectivelyrelease an item from an exemplary mobile node-enabled logisticsreceptacle by autonomously dropping the item from a secure captureconfiguration with respect to the mobile node-enabled receptacle (e.g.,secured in a storage position beneath an autonomous delivery vehiclethat includes a mobile master node operating as the node core of themobile node-enabled logistics receptacle) for an automatic deposit ofthe item at a particular address or desired location.

FIG. 36 is a flow diagram illustrating an exemplary method for enhanceddelivery management of an item using a mobile node-enabled logisticsreceptacle in accordance with an embodiment of the invention. Referringnow to FIG. 36, method 3600 begins at step 3605 with the mobilenode-enabled logistics receptacle (such as storage 3405 and master node3410) identifying an intended delivery location associated with theitem. The intended delivery location associated with the item may comefrom shipping information for the item that may have been preloaded intothe mobile node-enabled logistics receptacle's memory. If not, anembodiment of method 3600 may have the mobile node-enabled logisticsreceptacle detect a signal broadcast from a node associated with theitem, access the item's related shipping information from within thedetected signal, and identify the intended delivery location from theshipping information in the detected signal. Such shipping informationmay be part of, for example, header or other information broadcast as anadvertising signal (generally including message content) from node 3420a. In another embodiment, master node 3410 of the mobile node-enabledlogistics receptacle may receive the item's related shipping information(including the intended delivery location) from server 100 in responseto a request from master node 3410.

Furthermore, in the embodiments described herein, the intended deliverylocation for an item (and in some embodiments the rest of the shippinginformation, such as intended delivery time parameters) may share in asecure manner. For example, the shipping information or relevant partsof the shipping information may be encrypted to help protect theintegrity and security of such information. Those skilled in the artwill recognize various ways to securely encrypt information by a sourceand to securely decrypt the information by a recipient of theinformation in a manner that may involve secure identifiers, keys, keypairs, or establishing an active secure communication link between thesource and recipient. Sharing of such encrypted information may providea type of encrypted exchange of the shipping information.

In another example, a secure connection may be established between asource of the shipping information (e.g., a server or an ID nodeassociated with an item) and a recipient for the shipping information.As such, the secure connection may provide that any informationexchanged between the source and recipient is an encrypted exchange ofinformation that helps avoid sharing potentially sensitive informationwith other wireless devices and may help avoid nefarious devices fromspoofing what may otherwise appear to the recipient as authenticshipping information.

Thus, the intended delivery location for an item (and in someembodiments the rest of the shipping information, such as intendeddelivery time parameters) may be received by a node processing unit viaan encrypted/secure exchange relative to the detected signal from thesource of the shipping information as described herein.

As mentioned, a further embodiment may have the intended deliverylocation for the item as a recipient location, such as an address forthe recipient identified in the shipping information or, for example, alocation of a mobile user access device operative to function as a typeof node and where the mobile user access device is associated with arecipient for the item as indicated by the shipping information. And asnoted above, an embodiment may have the intended delivery location beinga type of way-point for a transition of ownership or temporary custodyof the item, or an ultimate delivery location for the item. For example,the intended delivery location for purposes of the embodiment may be afacility location (e.g., an address of a mail room) where the item maytransfer custody from a courier to a storage receptacle or room at thefacility so that other personnel may complete delivery of the item tothe ultimate delivery destination (e.g., a specific office within thefacility). Another example may have the intended delivery location beinga mobile location, such as the location of a courier's delivery van orthe location of a courier's mobile master node.

At step 3610, method 3600 continues with detecting a current location ofthe mobile node-enabled logistics receptacle. In the embodimentillustrated in FIG. 34, master node 3410, as part of a mobilenode-enabled logistics receptacle that includes storage unit 3405, maydetect its own current location using location circuitry onboard themaster node 3410 (such as GPS circuitry 475 as shown in FIG. 4 onexemplary master node 110 a). And while those skilled the art willappreciate this option of self-locating by the master node 3410, analternative embodiment may detect a current location of the mobilenode-enabled logistics receptacle by any of the location determinationtechniques described herein that may involve communicating with othersurrounding nodes, varying power levels, triangulating, and the like.

At step 3615, method 3600 proceeds by having the mobile node-enabledlogistics receptacle selectively release the item from the mobilenode-enabled logistics receptacle based upon the detected currentlocation of the mobile node-enabled logistics receptacle and theidentified intended delivery location. In more detail, an embodiment mayhave the mobile node-enabled logistics receptacle compare the detectedcurrent location of the mobile node-enabled logistics receptacle to theidentified intended delivery location. Based upon this comparison, themobile node-enabled logistics receptacle may release the item from astorage area within the mobile node-enabled logistics receptacle. Morespecifically, the mobile node-enabled logistics receptacle may releasethe item from the storage area when the comparison of the detectedcurrent location of the mobile node-enabled logistics receptacle to theidentified intended delivery location indicates the detected currentlocation of the mobile node-enabled logistics receptacle is within athreshold proximity area associated with the intended delivery location.For example, an exemplary threshold proximity area may include a defineddelivery area where a courier may drive or have a logistics vehiclesomewhere within that defined delivery area to drop off an item. Such adefined deliver area may be a block area near a destination addresswhere the current location of the logistics vehicle is within that blockarea, which allows for selective release of the item on that condition.

In another embodiment, step 3615 of method may involve a validation tooccur as the condition for selective release of the item. In particular,the step may have the mobile node-enabled logistics receptacleselectively release the item by establishing a validation connectionwith a node associated with the intended delivery location (e.g.,delivery location node 3440) to authorize releasing the item, and thenreleasing the item based upon the detected current location of themobile node-enabled logistics receptacle and the location of the mobileuser access device and after establishing the validation connection.Such a validation connection may involve establishing a securevalidation connection between the mobile node-enabled logisticsreceptacle and the mobile user access device in order to enhancesecurity when authorizing release of the item. In more detail, thevalidation connection may be implemented via a prompted connection withthe node associated with the intended delivery location that may allowfor a prompted validation request and receiving a validationconfirmation response from the node associated with the intendeddelivery location. In another embodiment, the validation connection maybe implemented to involve a preauthorized connection between the mobilenode-enabled logistics receptacle and the node associated with theintended delivery location that essentially has receipt of a signal(such as an advertising signal) from the delivery location node actingas the validation confirmation response without the need to haveinteractive prompts to request and then receive messages back and forthwith the mobile node-enabled logistics receptacle and the deliverylocation node. In this way, establishing a validation connection (suchas a secure validation connection) may provide a type of helpful,timely, and efficient confirmation that the item should be released.

In still a further embodiment, the selectively releasing step 3615 maybe implemented with the mobile node-enabled logistics receptacledetermining a proximity distance between the detected current locationof the mobile node-enabled logistics receptacle and the identifiedintended delivery location. Based on the determined proximity distance,the mobile node-enabled logistics receptacle may selectively actuate alockable opening to a storage area on the mobile node-enabled logisticsreceptacle to release the item. For example, armed with its ownself-locating circuitry and the shipping information having theidentified intended delivery location, master node 3410 may determinethat the current location of the master node 3410 (as its associatedstorage unit 3405) may be close enough in distance to the identifiedintended delivery location to actuate electronically actuated lockingelement 3515. In other words, the mobile node-enabled logisticsreceptacle may automatically unlock the lockable opening to a storagearea on the mobile node-enabled logistics receptacle to release the itemwhen the determined proximity distance is less than a thresholdproximity distance.

In a more detailed embodiment where the storage in the mobilenode-enabled logistics receptacle includes multiple storage areas (suchas that shown in FIG. 34), automatically unlocking to release the itemmay first involve identifying a portion of the storage area thatmaintains the item. This may be accomplished based on shippinginformation known the mobile node-enabled logistics receptacle for itemsstored within different storage areas of the receptacle. Afteridentifying the portion of the storage area that maintains the item, themobile node-enabled logistics receptacle may then automatically, unlockan access opening to the identified portion of the storage area (but notother portions of the storage area) to provide enhanced and selectivedelivery access to the appropriate item when the determined proximitydistance is less than the threshold proximity distance. In other words,the remaining part of the storage area not identified as maintaining theitem may remain in a locked state.

In yet another embodiment, method 3600 may have the mobile node-enabledlogistics receptacle receiving a delivery location signal broadcast froma node associated with the intended delivery location (such as a signalbroadcast from delivery location node 3440 in the embodiment illustratedin FIG. 34). As such, step 3615 of method 3600 may have the mobilenode-enabled logistics receptacle automatically unlocking an opening toa storage area maintaining the item upon or at least after receiving thedelivery location signal. In more detail, automatically unlocking theopening may, when dealing with storage in the mobile node-enabledlogistics receptacle that includes multiple storage areas, identifying aportion of the storage area that maintains the item. After identifyingthe portion, the mobile node-enabled logistics receptacle may thenautomatically, after receiving the delivery location signal, unlock anaccess opening to the identified portion of the storage area to providedelivery access to the item and may maintaining a locked state for theremaining portions of the storage area.

In a further embodiment where the intended delivery location is alocation of a mobile user access device operative to function as amaster node and associated with a recipient for the item (e.g., asindicated by the shipping information for the item), step 3615 of method3600 may have the mobile node-enabled logistics receptacle establishinga validation connection (such as a secure validation connection that mayinvolve encrypted and secure communications) with the mobile user accessdevice to authorize releasing the item. Accordingly, the mobilenode-enabled logistics receptacle may release the item from within themobile node-enabled logistics receptacle based upon the detected currentlocation of the mobile node-enabled logistics receptacle and thelocation of the mobile user access device but only after successfullyestablishing the validation connection as a further confirmation thatthe item should be released. In more detail and similar to thatdescribed above, the mobile node-enabled logistics receptacle mayestablish the validation connection by establishing an active promptedconnection between the mobile node-enabled logistics receptacle and themobile user access device. Through the active prompted connection, themobile node-enabled logistics receptacle may receive a promptedauthorization release acknowledgement (e.g., an electronic signaturerelease) from the mobile user access device in order to authorizereleasing the item.

Rather than an active prompted connection, the mobile node-enabledlogistics receptacle may establish the validation connection in anotherembodiment by establishing a preauthorized connection between the mobilenode-enabled logistics receptacle and the mobile user access device toautomatically authorize releasing the item. The preauthorizedconnection, for example, may be based upon a previously authorizedrelease validation condition that occurs automatically when the mobilenode-enabled logistics receptacle detects a signal broadcast as anadvertising signal from the mobile user access device related to therecipient of the item. For example, as shown in FIG. 34, an exemplarypreviously authorized release validation condition may be part ofshipping information related to item 3430 a and maintained in memory ofmaster node 3410. Such an exemplary previously authorized releasevalidation condition may indicate that detecting an advertising signalbroadcast from mobile user access device 3445 suffices as a validationcondition. Accordingly, when master node 3410 detects an advertisingsignal from mobile user access device 3445, the validation connectionmay be automatically established without prompts between the master node3410 and the mobile user access device 3445.

At step 3620, method 3600 may proceed with generating an alert relatedto releasing the item from the mobile node-enabled logistics receptacle.In some embodiments, the alert may be generated as information shown ona user interface of the mobile node-enabled logistics receptacle. Forexample, the alert may be generated as information shown on a display aspart of master node 3410, where the information alerts personnelregarding the released item and may provide location information for thereleased item to aid in accessing the released item. In anotherembodiment, the alert may be generated as a transmitted communication toanother node device, such as server 100, delivery location node 3440,and/or mobile user access device 3445.

Those skilled in the art will appreciate that method 3600 as disclosedand explained above in various embodiments may be implemented using anexemplary logistics receptacle having a mobile node at its core (such asexemplary master node 110 a as illustrated in FIG. 4 and master node3410 as illustrated in FIGS. 34 and 35A-35C) running one or more partsof a control and management code (such as a delivery release controlcode module) to implement any of the above described functionality. Suchcode may be stored on a non-transitory computer-readable medium (such asmemory storage 415 in an exemplary master node). Thus, when executingsuch code, a processing unit of the mobile master node (such as unit400) may be operative to perform operations or steps from the exemplarymethods disclosed above, including method 3600 and variations of thatmethod.

A more detailed embodiment of an exemplary mobile node-enabled logisticsreceptacle apparatus having enhanced delivery release control related toan item generally comprises a logistics receptacle (such as storage unit3405) and a node coupled to the logistics receptacle (such as masternode 3410). The logistics receptacle includes at least a storage (suchas storage 3415 a) for maintaining the item, and a lockable opening(such as lockable element 3505) through which the item and a nodeassociated with the item can pass into the storage area.

The node coupled to the logistics receptacle has a node processing unitas well as a node memory storage, location circuitry, an actuator, and acommunication interface. The node memory storage, location circuitry,actuator, and communication interface are each coupled to the nodeprocessing unit. The node memory storage maintains delivery releasecontrol code for execution by the node processing unit and may maintainshipping information related to the item. The location circuitry (suchas GPS circuitry) is operative to detect a location of the mobilenode-enabled logistics receptacle apparatus.

The actuator is coupled to the lockable opening and controlled by thenode processing unit to control access to the storage area bycontrolling a state of the lockable opening. The actuator, in oneembodiment, may be integrated as part of the node. However, in otherembodiments, the actuator may still be considered part of the node yetbe implemented with a separate physical device outside of a housing forthe node and driven by interfacing circuitry disposed within the housingfor the node. For example, electronically actuated locking element 3515is a type of actuator that may be deployed and considered as part of thenode yet is a physically separate device attached to storage unit 3405.

The node's communication interface is operative to access a wirelesscommunication path. As noted with respect to FIG. 4, an exemplarycommunication interface may embody a short-range communication interface(such as interface 480) or a medium/long range communication interface(such as interface 485) or a wireless communication interface capable ofhandling multiple data communication paths with separate formats (suchas one that collectively incorporates both interface 480 and interface485).

The node processing unit of the mobile node-enabled logistics receptacleapparatus, when executing the delivery release control code maintainedon the node memory storage, is operative to at least identify anintended delivery location associated with the item from the shippinginformation stored in the memory; cause the location circuitry to detecta current location of the mobile node-enabled logistics receptacleapparatus; and selectively cause the actuator to change the state of thelockable opening to an open state to provide delivery access to the itemwithin the storage area based upon the detected current location of themobile node-enabled logistics receptacle apparatus and the identifiedintended delivery location.

In a further apparatus embodiment, the communication interface maydetect a signal from the node associated with the item. In thissituation, the node processing unit may then be further operative toidentify the intended delivery location by receiving at least a portionof the detected signal from the communication interface; accessingshipping information within the portion of the detected signal, wherethe shipping information is related to the item; and identify theintended delivery location from the shipping information. As notedabove, the intended delivery location for an item (and in someembodiments the rest of the shipping information) may be encrypted orotherwise provided via a secure connection to help protect the integrityand security of such information.

In another embodiment of the apparatus, the node processing unit mayselectively cause the actuator to change to the open state by comparingthe detected current location of the mobile node-enabled logisticsreceptacle apparatus to the identified intended delivery location. Basedupon this comparison, the node processing unit may selectively cause theactuator to change the state of the lockable opening to the open state,such as when the comparison indicates the detected current location iswithin a threshold proximity area associated with the intended deliverylocation (e.g., a defined delivery area that would include the intendeddelivery location).

In a further apparatus embodiment, the node processing unit may beoperative to establish a validation connection, using the communicationinterface, with a node associated with the intended delivery location toauthorize releasing the item. Such a validation connection may involveestablishing a secure validation connection between the node processingunit and the node associated with the intended delivery location inorder to enhance security when authorizing release of the item. As such,the node processing unit may then cause the actuator to change the stateof the lockable opening to the open state based upon the detectedcurrent location of the mobile node-enabled logistics receptacle and thelocation of the mobile user access device and after successfullyestablishing the validation connection. Such a validation connection maybe, for example, a prompted connection with the node associated with theintended delivery location or a preauthorized connection between themobile node-enabled logistics receptacle and the node associated withthe intended delivery location.

Further still, an embodiment of the mobile node-enabled logisticsreceptacle apparatus may have the node processing unit being operativeto cause the actuator to unlock the lockable opening based upon aproximity distance between the detected current location of the mobilenode-enabled logistics receptacle apparatus and the identified intendeddelivery location. For example, the node processing unit may cause theactuator to automatically unlock the lockable opening to the storagearea when the determined proximity distance is less than a thresholdproximity distance (such as when the location of the mobile node-enabledlogistics receptacle is within 100 yards of an intended deliverylocation for an item).

In another embodiment, the node processing unit may receive a deliverylocation signal from the communication interface, where the deliverylocation signal is being broadcast from a node associated with theintended delivery location. In such a situation, the node processingunit may cause the actuator to automatically unlock the lockable openingafter receiving the delivery location signal. As such, receipt of thedelivery location signal may indicate that the mobile node-enabledlogistics receptacle apparatus sufficiently near the intended deliverylocation. Such a node associated with the intended delivery location maybe a mobile node associated with the intended delivery location (such asmobile user access node 3445 when it shipping information for the itemidentified the location of node 3445 as the intended delivery location)or a fixed node associated with the intended delivery location (such asa facility centric fixed delivery location node (e.g., node 3440)).

Embodiments of the mobile node-enabled logistics receptacle apparatusmay also generate and provide an alert when selectively releasing theitem. In more detail, an embodiment may have the node processing unitgenerating an alert related to release of the item from the mobilenode-enabled logistics receptacle. For example, the node processing unitmay cause the communication interface to transmit the alert to a nodeassociated with the intended delivery location. In another example, thenode processing unit may display the generated alert on a user interfacecoupled to the node processing unit of the mobile node-enabled logisticsreceptacle apparatus. In a further example, the user interface mayimplement a speaker and the node processing unit may generate the alertby playing an auditory alert with the speaker.

As noted above, the intended delivery location may comprise a recipientrelated location, such as a location of a mobile user access deviceidentified in the shipping information and associated with a recipientfor the item (e.g., mobile user access device 3445 show in theembodiment illustrated in FIG. 34). In such an embodiment, the nodeprocessing unit may establish a validation connection (such as a securevalidation connection using the communication interface for an encryptedexchange of information) with mobile user access device to authorizereleasing the item and cause the actuator to change the state of thelockable opening to the open state based upon the detected currentlocation of the mobile node-enabled logistics receptacle and thelocation of the mobile user access device and after successfullyestablishing the validation connection. In more detail, the validationconnection may be established with an active prompted connection betweenthe mobile node-enabled logistics receptacle apparatus (e.g., the nodepart of the apparatus) and the mobile user access device over thewireless communication path to receive a prompted authorization releaseacknowledgement from the mobile user access device in order to authorizereleasing the item. In another example, the validation connection mayhave the node processing unit establishing a preauthorized connectionbetween the mobile node-enabled logistics receptacle apparatus and themobile user access device over the wireless communication path toautomatically authorize releasing the item without the need forinteractive prompts. Such a preauthorized connection may allow the nodeprocessing unit to automatically cause the actuator to release the itembased upon a previously authorized release validation condition thatoccurs automatically when the mobile node-enabled logistics receptacledetects a signal broadcast as an advertising signal from the mobile useraccess device related to the recipient of the item.

The above description of an exemplary mobile node-enabled logisticsreceptacle apparatus may be extended to a system embodiment where thelogistics receptacle may be implemented with a logistics vehicle. Inmore detail, an exemplary node-enabled logistics vehicular system havingenhanced delivery release control related to an item comprises alogistics vehicle and a master node disposed on the logistics vehicle.The logistics vehicle (such as vehicle 3400 shown and explained withreference to FIG. 34) includes a first storage area for maintaining theitem and a first lockable opening through which the item and a noderelated to the item can pass into the storage area. Such a lockableopening acts a barrier or obstruction that helps prevent unintentionallyremoving an item from the storage area.

In this exemplary system embodiment, the master node disposed on thelogistics vehicle comprises a node processing unit, a node memorystorage, location circuitry, a first actuator, a first communicationinterface, and a second communication interface. The node processingunit is operatively coupled to each of the node memory storage, locationcircuitry, first actuator, first communication interface, and secondcommunication interface. In more detail, the node memory storagemaintains an embodiment of delivery release control code for executionby the node processing unit and may also include shipping informationrelated to the item (e.g., shipping information that has been preloadedor actively provided to the master node by a server or provided by thenode related to the item). The location circuitry on the master node(such as GPS circuitry and antenna 475 on exemplary master node 110 a)is operative to detect a location of the logistics vehicle given thelogistics vehicle and the mobile nature of the logistics vehicle. Thefirst actuator (similar to the actuator discussed above relative to themobile node-enabled logistics receptacle apparatus) is coupled to thenode processing unit and the first lockable opening, and controls accessto the first storage area by controlling a state of the first lockableopening.

The master node further includes the first communication interface thatcan communicate with at least the node related to the item over a firstwireless communication path and the second communication interface thatcan communicate with a server over a second wireless communication path.As discussed, the first communication interface may be a short rangeinterface, such as a Bluetooth® Low Energy type of radio interface,while the second communication interface may be a longer rangeinterface, such as a Wi-Fi or cellular wireless radio interface.

As part of this exemplary system embodiment, the node processing unit ofthe master node, when executing the delivery release control codemaintained on the node memory storage, becomes specially adapted andoperative to at least identify an intended delivery location associatedwith the item from the shipping information stored in the memory; causethe location circuitry to detect a current location of the logisticsvehicle; and selectively cause the first actuator to change the state ofthe first lockable opening to an open state to provide delivery accessto the item within the first storage area based upon the detectedcurrent location of the logistics vehicle and the identified intendeddelivery location.

In some further system embodiments, the first communication interfacemay be able to detect a signal broadcast from the node related to theitem. As a result, the node processing unit may operate to identify theintended delivery location by identifying the intended delivery locationbased upon a portion of the detected signal, where the portion of thedetected signal includes broadcast data indicating the shippinginformation for the item. As noted above, the intended delivery locationfor an item (and in some embodiments the rest of the shippinginformation) may be encrypted or otherwise provided in an encryptedexchange of the shipping information via a secure connection to helpprotect the integrity and security of such information.

In a more detailed system embodiment, the node processing unit mayselectively cause the first actuator to change to the open state whenthe detected current location of the logistics vehicle is within aproximity service area associated with the intended delivery location.In another system embodiment, the node processing unit may selectivelycause the first actuator to change the state of the first lockableopening to the open state by being further operative to cause the firstactuator to unlock the first lockable opening when a proximity distancebetween the detected current location of the logistics vehicle and theidentified intended delivery location is less than a threshold proximitydistance.

In still another system embodiment, the node processing unit may receivea delivery location signal from the first communication interface orfrom the second communication interface. The delivery location signal isbroadcast from a node associated with the intended delivery location andthe format and communication path used by the broadcasting node willdictate which of the communication interfaces may detect the deliverylocation signal and provide it to the node processing unit (or notifythe node processing unit about detecting the delivery location signal).Upon or after receiving the delivery location signal, the nodeprocessing unit may then cause the first actuator to automaticallyunlock the first lockable opening. Thus, receipt of the deliverylocation signal in this embodiment operates as a condition forappropriately releasing the item from the vehicle's storage area. Thebroadcasting node may, for example, be a mobile node associated with theintended delivery location or a fixed node associated with the intendeddelivery location.

In a further system embodiment, the node processing unit may beoperative to cause the second communication interface to transmit analert to a node associated with the intended delivery location (such asdelivery location node 3440 or mobile user access device 3445 operatingas a node). Such an alert relates to the delivery access to the itembased upon the open state of the first lockable opening.

In yet another system embodiment, the logistics vehicle may havemultiple storage areas. More specifically, an embodiment of thelogistics vehicle may further comprises a second storage area and asecond lockable opening through which to access the second storage area(such as that shown in FIG. 34 with multiple storage areas 3415 a-3415c). In such an embodiment, the master node in the system may furthercomprise a second actuator operatively coupled to the second lockableopening and controlled by the node processing unit, so that the secondactuator controls access to the second storage area by controlling astate of the second lockable opening. With these additional elements,the node processing unit of the master node may then be furtheroperative to selectively cause the first actuator to change the state ofthe first lockable opening to the open state to provide delivery accessto the item within the first storage area based upon the detectedcurrent location of the logistics vehicle and the identified intendeddelivery location while causing the second actuator to maintain thestate of the second lockable opening in a closed state to prevent accessto what is stored within the second storage area.

Enhanced Delivery Notifications

As mentioned above, elements of an exemplary wireless node network maybe deployed in improved logistics applications where elements may sensean adverse delivery condition in a proactive and more timely manner thatinvolves relevant and enhanced corrective delivery or pickupnotifications to address the sensed condition (e.g., when an item hasbeen dropped off or picked up without meeting certain deliveryparameters, such as delivery to or pickup from the intended destination,pickup by incorrect logistics personnel, or delivery/pickup during anintended time period, or a combination of such conditions). The use ofenhanced delivery notifications may involve a mobile master nodeinvolved in the pickup or delivery of an item (such as courier's mobilemaster node) and may involve a master node at a particular location(such as a mailroom facility master node or a mobile user access deviceoperating as a type of master node (e.g., a smartphone associated with ashipping customer having an item picked up from the particular locationor a smartphone associated with a recipient of the item that is waitingfor the item to be dropped off at the particular location)). Bothperspectives of how enhanced delivery related notifications may begenerated and used with these types of master nodes are described inmore detail below with respect to the diagrams of such nodes shown inFIGS. 37A-37C and in the flow diagrams that provide further detail inFIGS. 38-42.

FIGS. 37A-37C are diagrams illustrating an exemplary mobile couriermaster node moving between locations with items for delivery or pickupin accordance with embodiments of the invention. Referring now to FIG.37A, server 100 is shown connected to network 105 (similar to that shownin FIG. 1). In more detail, server 100 is coupled through network 105 tovarious master nodes disposed at different physical locations. Masternode 3705 a is at location 1 and master node 3705 b is at location 2.For example, location 1 may be an office mailroom location and masternode 3705 a may be a facility type of master node associated with theoffice mailroom or a mobile user access device operating as a masternode and associated with a shipping customer for an item to be shippedfrom location 1 or a recipient for an item to be delivered to location1. Location 2 may be a residential location and master node 3705 b maybe a mobile user access device operating as a type of mobile master nodeassociated with a recipient living at the residential location.

In the contextual environment of these two different locations, theembodiment shown in FIG. 37A also includes a mobile courier master node3710 involved in delivering items 3700 a and 3700 b and picking up item3700 c. Consistent with exemplary master node 110 a shown and describedin FIG. 4, mobile courier master node 3710 is shown including a userinterface having a speaker 3725 and a display 3730 (such as anelectronic ink display or ruggedized touchscreen display). As will beexplained in more detail below, such a user interface may presentexemplary corrective delivery notifications generated by the mobilemaster node 3710 and/or master nodes at particular physical locations(such as master node 3705 a and 3705 b).

While items 3700 c and 3700 d are initially located at location 1 nearmaster node 3705 a as shown in FIG. 37A, items 3700 a and 3700 binitially accompany mobile courier master node 3710. For example, mobilecourier master node 3710 may be a handheld node device (e.g., aruggedized tablet type of device) associated with particular logisticspersonnel responsible for delivering items 3700 a and 3700 b to theirrespective intended delivery locations. As previously noted, anexemplary intended delivery location may be considered as a transitionpoint for transition of custody (such as a mailroom type of way-pointlocation that will receive custody of an item, sort and process theitem, and further transition custody of the item to other personnel forfurther delivery operations) or an ultimate delivery location for theitem. As previously noted, an exemplary intended delivery location mayalso be identified as a physical address or location (such as aresidential address or office address) or may be identified withreference to a current location of a specific mobile user access deviceor other node. Thus, the items 3700 a and 3700 b may move with mobilecourier master node 3710 toward different locations where an item may bedropped off, subject to a custody transfer, or be personally deliveredto a particular recipient.

FIG. 37B shows a further snapshot of items 3700 a-3700 d and mobilecourier master node 3710 after mobile courier master node 3710 has movedpast location 1 and is moving towards location 2. In FIG. 37B, item 3700a has been dropped off and item 3700 d has been picked up with respectto mobile courier master node 3710. More specifically, as shown in FIG.37B, item 3700 a is dropped off at location 1 and no longer accompaniesmobile courier master node 3710. Thus, item 3700 a remains stationarywith respect to location 1 where master node 3705 a is disposed. Inother words, item 3700 a (and its related ID node 3720 a) may beconsidered to have been left in location 1 rather than continue toaccompany mobile courier master node 3710 and item 3700 b (and itsrelated ID node 3720 b) as they continue to move towards location 2where master node 3705 b is disposed.

Item 3700 d has been picked up from location 1 and is now accompanyingmobile courier master node 3710. As such, where item 3700 c remainsstationary with respect to location 1 where master node 3705 a isdisposed, item 3700 d is now moving as it accompanies mobile couriermaster node 3710 towards location 2 where master node 3705 b isdisposed.

In a delivery/pickup situation, an adverse delivery or pickup conditionmay be sensed by one or more of the master nodes shown in FIGS. 37A-37C.In general, an exemplary adverse delivery condition is a sensedcondition that creates a current or potential issue inconsistent withproper delivery of an item. For example, an exemplary adverse deliverycondition may be location related, such as an item being at an incorrectlocation for delivery (e.g., where the item may be mistakenly deliveredto the wrong location or is approaching a location that is not itsintended delivery location), or an item moving away from its intendeddelivery location (e.g., where the item may have missed being deliveredto the correct location). An exemplary adverse pickup condition may alsobe location related, such as for an item staying at a location when itwas supposed to transition custody to an intended pickup master nodethat left the location (e.g., where the item pickup was missed), or anitem moving away from its intended pickup location after transitioningcustody to mobile courier master node that does not correspond to theintended pickup master node (e.g., where the item was incorrectly pickedup and may be heading out of a warehouse unexpectedly).

An exemplary adverse delivery condition may also involve a time relatedcondition, such as a delivery deadline or a delivery time range. Furtherexemplary adverse delivery conditions may involve a combination oflocation related conditions and time related conditions that may besensed and, in response, have an appropriate corrective deliverynotification generated and, in some instances, transmitted to anothernode where appropriate. FIGS. 38 and 39 explain exemplary methods of howdifferent master nodes (such as those shown in FIGS. 37A and 37B) mayreact by automatically sensing a type of adverse delivery condition andgenerating a corrective delivery notification accordingly in differentembodiments as described in more detail below.

FIG. 38 is a flow diagram illustrating an exemplary method forgenerating a corrective delivery notification related to an item by amobile master node involved with delivery of the item in accordance withan embodiment of the invention. Referring now to FIG. 38, exemplarymethod 3800 begins at step 3805 by identifying an intended deliverylocation related to an item by a mobile master node involved with adelivery of the item (such as a mobile courier master node). Theintended delivery location may be identified from shipping informationrelated to the item. In some embodiments, the mobile master node maydetect a signal broadcast from an ID node associated with the item andthen accessing the shipping information from within the detected signal.In this manner, the intended delivery location may be identified fromthe shipping information. In other embodiments, the mobile master nodemay receive shipping information from a server (such as in a preloadingmessage coming from the server or in a response from the server to ashipping information request from the mobile master node). The intendeddeliver location for the item may then be identified from the shippinginformation received from the server, which may be received as encryptedinformation and/or via a secure communication path established with theserver.

For example, as shown in FIG. 37A, mobile courier master node 3710 mayidentify an intended delivery location for each of items 3700 a and 3700b. Server 100 may provide shipping information that identifies therespective intended delivery locations for each of items 3700 a and 3700b or mobile courier master node 3710 may identify the respectiveintended delivery locations from signals broadcast from ID nodes 3720 aand 3720 b (such as via encrypted shipping information and/or via anappropriate secure connection between mobile courier master node 3710and the source of the shipping information—e.g., server 100 or ID nodes3720 a and 3720 b). Such signals may be short range advertising signalsbroadcast in a Bluetooth® format and have shipping information(including data that reflects the intended delivery location) as part ofthe respective packets in the signals. Thus, mobile courier master node3710 may be made aware of the respective intended delivery locations foritems 3700 a and 3700 b that accompany master node 3710.

At step 3810, method 3800 continues with location circuitry within themobile master node detecting a current location of the mobile masternode. As noted with respect to FIG. 4, an exemplary master node 110 aincludes location positioning circuitry 475, such as GPS circuitry, thatallows the master node to self-locate its current location. Thoseskilled in the art will appreciate that the location circuitry on amaster node may also involve other techniques for locating the masternode by itself or with the assistance of other nodes, as described inmore detail above.

At step 3815, method 3800 proceeds with the mobile master nodeautomatically sensing an adverse delivery condition related to the itembased upon the intended delivery location and the current location ofthe mobile master node. As generally noted above, an adverse deliverycondition may be considered a condition that creates a current orpotential issue inconsistent with proper delivery of an item. In a moredetailed embodiment, the mobile master node may automatically sense theadverse delivery condition as an incorrect location for delivery of theitem based upon a comparison of the identified intended deliverylocation and the detected current location of the mobile master node.More specifically, the step of automatically sensing the incorrectlocation may involve comparing the current location of the mobile masternode to a proximity distance threshold related to the identifiedintended delivery location. For example, mobile courier master node 3710may automatically sense an incorrect location for delivering item 3700 aif the current location of mobile courier master node 3710 is outside ofa proximity distance threshold of 100 yards from the intended deliverylocation of item 3700 a. In other words, a comparison of the location ofmobile courier master node 3710 to a proximity distance threshold zonearound the intended delivery location for item 3700 a may provide abasis for sensing a type of adverse delivery condition relative to item3700 a.

In a further embodiment of method 3800, step 3815 may have the mobilemaster node sensing the adverse delivery condition as a movement awayfrom the intended delivery location based upon the identified intendeddelivery location and the detected current location of the mobile masternode. In more detail, the mobile master node may automatically sense amovement direction associated with the mobile master node and comparethe determined movement direction and the current location of the mobilemaster node to the intended delivery location. The two locations (i.e.,that of the mobile master node and the intended delivery location) aswell as the direction the mobile master node is moving allows the mobilemaster node to identify the adverse delivery condition as whether themobile master node is moving away from the intended delivery location.For example, mobile courier master node 3710 as shown in FIG. 37B maysense its own movement away from location 1 based upon successiveself-location determinations. Mobile courier master node 3710 may then,armed with its direction of movement relative to its current location,automatically sense an adverse delivery condition for item 3700 b whenthe intended location for item 3700 b is location 1.

In still another embodiment of method 3800, step 3815 may also involvean intended delivery time parameter related to an item. The mobilemaster node may have received the intended delivery time parameterrelated to the item as part of shipping information related to thedelivery of the item (e.g., provided by a server or by an ID nodeassociated with the particular item). As such, the adverse deliverycondition may also be based upon the intended delivery time parameter,such as a delivery deadline (e.g., delivery for the particular item isappropriate if done prior to 5 pm or done on a particular day) and adelivery time range (e.g., delivery for the particular item isappropriate if done within a range of times/days). Thus, adversedelivery conditions for each item may be based upon location relatedconditions, time related conditions, and/or a combination of both.

At step 3820, method 3800 continues with the mobile master node,generating the corrective delivery notification based upon the adversedelivery condition sensed in step 3815. In a further detailed embodimentwhere the mobile master node may be associated with a courier (generallyreferring to personnel involved with the delivery of the item),generating the corrective delivery notification may have the mobilemaster node automatically prompting the courier with the correctivedelivery notification. This may be accomplished, for example, bygenerating an alert sound by the mobile master node (e.g., a soundgenerated through speaker 3725 of mobile courier master node 3710)and/or generating electronic feedback for the courier on a userinterface of the mobile master node. Such user interface feedback may bepresented in the form electronic feedback information for the courier ona display on the user interface (e.g., information presented on display3730 of mobile courier master node 3710).

The corrective delivery notification, for example, may includecautionary and/or instructive feedback relative to the sensed adversedelivery condition. For example, the notification may include aninstruction not to deliver the item based upon the adverse deliverycondition. This may be appropriate when the mobile master node's currentlocation is inconsistent with the identified intended delivery location(e.g., they do not match up, not within a threshold distance from theintended delivery location, etc.). In another example, the notificationmay involve a displayed instruction to alter a current direction ofmovement based upon the adverse delivery condition or, in more detail,to move to a specified location (e.g., an alternative location comparedto the mobile master node's current location, a prior location of themobile master node, the identified intended delivery location (which isnot matching up with the mobile master node's current location)).

Those skilled in the art will appreciate that method 3800 as disclosedand explained above in various embodiments may be implemented using anexemplary mobile master node (such as exemplary master node 110 a asillustrated in FIG. 4 and mobile courier master node 3710 as illustratedin FIGS. 37A and 37B) running one or more parts of a control andmanagement code (such as a delivery notification code module) toimplement any of the above described functionality. Such code may bestored on a non-transitory computer-readable medium (such as memorystorage 415 in an exemplary master node). Thus, when executing suchcode, a processing unit of the mobile master node (such as unit 400) maybe operative to perform operations or steps from the exemplary methodsdisclosed above, including method 3800 and variations of that method.

Another embodiment of an exemplary mobile master node apparatus involvedwith a delivery of an item and a corrective delivery notificationgenerally comprises a node processing unit, node memory storage,location circuitry, and one or more communication interfaces. The nodeprocessing unit is coupled to each of the node memory storage, locationcircuitry, and communication interface(s). The node memory storagemaintains delivery notification code for execution by the nodeprocessing unit. The location circuitry is operative to detect a currentlocation of the mobile master node apparatus. The communicationinterface is operative to access a wireless communication path and may,in some embodiments, include different interfaces to accommodatedistinct wireless communication paths to different devices usingdifferent ranges and formats for communications. The node processingunit, when executing the delivery notification code maintained on thenode memory storage, is specially adapted to become operative toidentify an intended delivery location associated with the item fromshipping information related to the item; cause the location circuitryto detect a current location of the mobile master node; automaticallydetermine an adverse delivery condition related to the item based uponthe intended delivery location and the detected current location of themobile master node; and generate a corrective delivery notificationbased upon the determined adverse delivery condition related to theitem.

In a further apparatus embodiment, the node memory storage may maintainthe shipping information related to the item. In more detail, theshipping information may comprise an intended delivery time parameterrelated to the item (such as a delivery deadline or a delivery timerange as explained above with reference to FIG. 38). As such, the nodeprocessing unit may automatically determine the adverse deliverycondition based upon the intended delivery location, the detectedcurrent location of the mobile master node, and the intended deliverytime parameter.

In still another apparatus embodiment, the node processing unit may befurther operative to receive the shipping information related to theitem from a second node or device, such as an ID node associated withthe item (such as ID node 3720 a) or a server (such as server 100). Inmore detail, the ID node may be in operative communication with themobile master node apparatus over the communication interface (e.g., ashort range part of the interface operative to communicate using aBluetooth® Low Energy radio interface). In another embodiment where theshipping information is provided from the server, such a server may bein operative communication with the mobile master node apparatus overanother part of the communication interface (e.g., a longer range partof the interface operative to communicate using a cellular radiointerface or Wi-Fi wireless interface).

In yet another apparatus embodiment, the node processing unit may beoperative to automatically determine the adverse delivery condition byautomatically sensing the adverse delivery condition as an incorrectlocation for delivery of the item based upon a comparison of theidentified intended delivery location and the detected current locationof the mobile master node apparatus. More specifically, the nodeprocessing unit may compare the current location of the mobile masternode apparatus to a proximity distance threshold related to theidentified intended delivery location. This may allow the nodeprocessing unit to determine if the current location of the mobilemaster node apparatus is sufficiently close to the identified intendeddelivery location to avoid generating a warning or notification relatedto delivery of the item in question.

In a further apparatus embodiment, the node processing unit may beoperative to automatically determine the adverse delivery condition byautomatically sensing the adverse delivery condition as a movement ofthe mobile master node apparatus away from the intended deliverylocation based upon the identified intended delivery location and thedetected current location of the mobile master node apparatus. In moredetail, the node processing unit may interact with the locationcircuitry in this further detailed embodiment to determine a movementdirection associated with the mobile master node apparatus over a periodof time. For example, mobile courier master node 3710 as shown in FIG.37B may determine it is moving in a direction towards location 2 bytaking successive location measurements (e.g., detecting a series of GPScoordinates reflecting movement and a direction of movement for themobile courier master node 3710). In this manner, the node processingunit may automatically sense movement of the mobile master nodeapparatus (such as mobile courier master node 3710) away from theintended delivery location based upon a comparison of the determinedmovement direction and the detected current location of the mobilemaster node relative to the intended delivery location.

Additional apparatus embodiments may generate and provide the correctivedelivery notification in a variety of ways. For example, when the mobilemaster node apparatus is associated with a courier involved with thedelivery of the item, the node processing unit may generate thecorrective delivery notification by automatically prompting the courierwith the corrective delivery notification. Such prompting may beimplemented with a speaker on the apparatus and operatively coupled tothe node processing unit, and where the node processing unit maygenerate an alert sound on the speaker. In another example, suchprompting may be implemented using a user interface on the apparatus andoperatively coupled to the node processing unit, and where the nodeprocessing unit may generate electronic feedback for the courier on theuser interface of the mobile master node apparatus. In more detail, theuser interface may be implemented with a display and the electronicfeedback for the courier may include an instruction not to deliver theitem based upon the adverse delivery condition, an instruction to altera current direction of movement based upon the adverse deliverycondition, and/or an instruction to move to a specified location. Forexample, such a specified location may include an alternative locationcompared to the mobile master node's current location, a prior locationof the mobile master node, or the identified intended delivery location.Thus, the corrective delivery notification allows for automaticcautionary and/or instructive feedback in a timely manner that enhancesand improves a monitored delivery process for an item.

While FIG. 38 explains an exemplary method involving a correctivedelivery notification from the perspective of a mobile master node (suchas mobile courier master node 3710), FIG. 39 is a flow diagramillustrating an exemplary method for transmitting a corrective deliverynotification related to an item from the perspective of a master node ata particular location (such as master node 3705 a at location 1 in theembodiment shown in FIG. 37B). Referring now to FIG. 39, method 3900begins at step 3905 with a first master node at a first locationreceiving shipping information related to the item. The first masternode may, for example, receive the shipping information as part of abroadcasted signal from an ID node associated with the item (such aswhen ID node 3720 a associated with item 3700 a approaches location 1and broadcasts an advertising signal that may include shippinginformation related to item 3700 a). In another embodiment, the firstmaster node may receive the shipping information as part of a preloadingmessage from a server in communication with the first master node (suchas when server 100 is aware of an anticipated path of item 3700 a andits associated ID node 3720 a, and server 100 transmits shippinginformation related to item 3700 a to master node 3705 a at location 1).In some embodiments, the server may provide or transmit the shippinginformation to the first master node as a response to a shippinginformation request from the first master node (such as when master node3705 a detects item 3700 a approaching or at location 1 and sends server100 a shipping information request relative to item 3700 a). Requestsand receipt of the information from other nodes may be accomplished, insome embodiments, via a secure connection that may deploy encryption tohelp secure and protect the shipping information as sensitiveinformation and to help avoid issues with improper signals beingidentified from nodes not intended to be related to delivery or pickupof the item.

At step 3910, method 3900 continues by parsing the received shippinginformation to identify an intended delivery location related to theitem. For example, the shipping information may include a variety ofdata related to the item, such as an identification of the recipient, adestination address, a description of the item, as well as informationon intermediate way-points where custody of the item may be transferred.The first master node at the first location may analyze the received orstored shipping information to sift out and identify an intendeddelivery location for the item (e.g., the destination address where theitem may ultimately be delivered into the custody of the recipient, oran intermediate location where the item may be transferred in custodywhile being tracked and monitored via the back-end server 100).

At step 3915, method 3900 continues with the first master nodeautomatically sensing an adverse delivery condition related to the itembased upon the first location of first master node and the intendeddelivery location for the item. Thus, step 3915 has a different type ofmaster node sensing the adverse delivery condition and reacting thanthat described with respect to FIG. 38. In more detail, the first masternode may automatically sense the adverse delivery condition bydetermining a difference between the first master node's location (i.e.,the first location) and the intended delivery location for the item whenan ID node associated with the item arrives at the first location. Sucha determined difference may indicate an incorrect location for deliveryof the item as the adverse delivery condition and as viewed by the firstmaster node.

In another embodiment, the first master node may automatically sense theadverse delivery condition by determining the first location does notcorrespond to the intended delivery location for the item, and thendetecting when an ID node associated with the item is proximate andstationary relative to the first master node when the courier masternode is moving away from the first location. Here, the detectedstationary location of the ID node reflects an incorrect location fordelivery of the item as the adverse delivery condition when the couriermaster node is detected to be moving away from the first master node'slocation. In such an embodiment, the first master node may request othernode's locations (such as the location of the courier master node) andmay determine the location of some nodes (such as the location of thefirst master node and/or the location of the ID node associated the itemthat is no longer moving with the courier master node).

In still another embodiment, the automatically sensing step may beaccomplished when the first master node detects movement of an ID nodeassociated with the item away from the first master node's location asthe adverse delivery condition when the first location corresponds tothe intended delivery location. For example, master node 3705 a maydetect movement of ID node 3720 b as moving away from location 1 (thelocation of master node 3705 a). Should the intended delivery locationof item 3700 b correspond to location 1, master node 3705 a may thusautomatically sense an adverse delivery condition.

In a further embodiment of method 3900, the shipping information mayalso include an intended delivery time parameter related to delivery ofthe item (such as a delivery deadline or delivery timeframe) such thatthe adverse delivery condition may also be based upon whether theintended delivery time parameter is consistent with delivery of the itemat that time.

At step 3920, method 3900 continues with the first master nodetransmitting the corrective delivery notification to a courier masternode based upon the adverse delivery condition sensed by the firstmaster node. For example, if master node 3705 a senses item 3700 a hasbeen left at location 1, which is determined to be an incorrect locationfor delivery of item 3700 a (based upon shipping information related toitem 3700 a), master node 3705 a may transmit a corrective deliverynotification to mobile courier master node 3710 identifying item 3700 aas being at an incorrect location for delivery.

The exemplary corrective delivery notification transmitted to a couriermaster node may include cautionary and instructive information thatimproves and enhances the delivery process. For example, the correctivedelivery notification transmitted to the courier master node may includeat least an instruction not to deliver the item to the first location ofthe first master node, which may help proactively avoid an incorrect orinappropriate delivery prior to it occurring. In another example, thecorrective delivery notification transmitted to the courier master nodemay identify the item as not being delivered to the intended deliverylocation, which may timely inform the courier master node of a misseddelivery of the item. In more detail, such a corrective deliverynotification may include an instruction to the courier master node tomove to a specified location, such as the first location of the firstmaster node, an alternative location, or to the previously identifiedintended delivery location, to allow for appropriate delivery of theitem.

Those skilled in the art will appreciate that method 3900 as disclosedand explained above in various embodiments may be implemented using anexemplary master node (such as exemplary master node 110 a asillustrated in FIG. 4 and master nodes 3705 a and 3705 b as illustratedin FIGS. 37A and 37B) running one or more parts of a control andmanagement code (such as a delivery notification code module) toimplement any of the above described functionality. Such code may bestored on a non-transitory computer-readable medium (such as memorystorage 415 in an exemplary master node). Thus, when executing suchcode, a processing unit of the mobile master node (such as unit 400) maybe operative to perform operations or steps from the exemplary methodsdisclosed above, including method 3900 and variations of that method.

Another embodiment of an exemplary master node apparatus disposed at afirst location and in communication with a courier master node involvesa corrective delivery notification. Such an exemplary master nodeapparatus generally comprises a node processing unit, node memorystorage, location circuitry, and one or more communication interfaces.The node processing unit is coupled to each of the node memory storage,location circuitry, and communication interface(s). The node memorystorage maintains delivery notification code for execution by the nodeprocessing unit. The location circuitry is operative to detect a currentlocation of the master node apparatus. The communication interface isoperative to access a wireless communication path and may, in someembodiments, include different interfaces to accommodate distinctwireless communication paths to different devices using different rangesand formats for communications. The node processing unit, when executingthe delivery notification code maintained on the node memory storage, isspecially adapted to become operative to receive shipping informationvia the communication interface, the shipping information being relatedto the item; store the received shipping information in the node memorystorage; parse the received shipping information to identify an intendeddelivery location for the item; cause the location circuitry to detectthe current location of the master node apparatus as the first location;automatically sense an adverse delivery condition related to the itembased upon the first location of master node apparatus and the intendeddelivery location for the item; and cause the communication interface totransmit a corrective delivery notification to the courier master nodebased upon the adverse delivery condition.

In a further apparatus embodiment, the node processing unit of themaster node apparatus at the first location may automatically sense theadverse delivery condition by determining a difference between the firstlocation and the intended delivery location for the item when an ID nodeassociated with the item arrives at the first location. Such adetermined difference may indicate an incorrect location for delivery ofthe item as the adverse delivery condition.

In another apparatus embodiment, the node processing unit of the masternode apparatus at the first location may automatically sense the adversedelivery condition by comparing the first location to the intendeddelivery location to determine if the first location does not correspondto the intended delivery location for the item. The node processing unitmay then detect that an ID node associated with the item is proximateand stationary relative to the first master node while also detectingthat the courier master node is moving away from the first location.Under monitoring conditions, the node processing unit of the master nodeapparatus may determine the ID node is in an incorrect location fordelivery of the item as the adverse delivery condition when (a) thefirst location does not correspond to the intended delivery location forthe item, (b) the ID node associated with the item is detected to beproximate and stationary relative to the master node apparatus, and (c)the courier master node is detected to be moving away from the firstlocation. This reflects how the first master node may sense an itemincorrectly left at its location and be operative to signal the couriermaster node with a relevant and responsive corrective deliverynotification that improves and enhances the monitored delivery processinvolving the master node apparatus.

Further still, the node processing unit may automatically sense theadverse delivery condition by detecting a movement of an ID nodeassociated with the item away from the first location as the adversedelivery condition when the first location corresponds to the intendeddelivery location. In other words, when the item's intended deliverylocation corresponds to the location of the master node apparatus andthe item's associated ID node is detected as moving away from the masternode apparatus' location, the master node apparatus automatically sensesa type of adverse delivery condition reflecting the item was notdelivered to the correct location.

The corrective delivery notification to the courier master node mayreflect and include cautionary and instructive information. For example,the corrective delivery notification to the courier master node mayidentify the item as being at an incorrect location for delivery, mayinclude an instruction not to deliver the item to the first location ofthe master node apparatus, and may identify the item as not beingdelivered to the intended delivery location. Furthermore, the correctivedelivery notification to the courier master node may include aninstruction to the courier mobile master node to move to a specifiedlocation, such as an alternative location, a prior location of thecourier master node, or to reiterate and remind the courier of theitem's intended delivery location so that timely corrective deliveryaction may be initiated.

As with some of the other embodiments, a further embodiment of themaster node apparatus may have the node processing unit receiving theshipping information over the communication interface from an ID nodeassociated with the item (or one of the communications interfacesdeployed on the master node apparatus capable of closer rangecommunications with the ID node). In this scenario, the ID node mayprovide the shipping information over the wireless communication path aspart of a broadcasted signal from the ID node, such as a Bluetooth®formatted signal. In another embodiment, the node processing unit mayreceive the shipping information over the communication interface from aserver (or one of the communications interfaces deployed on the masternode apparatus capable of longer range communications with the server).In this scenario, the server may provide the shipping information in apreloading message from the server or, alternatively, provide theshipping information in response to a shipping information requesttransmitted to the server. As noted above, the intended deliverylocation for an item (and in some embodiments the rest of the shippinginformation) may be encrypted or otherwise provided via a secureconnection to help protect the integrity and security of suchinformation.

In still another apparatus embodiment, the shipping information mayinclude an intended delivery time parameter related to the item. Assuch, the node processing unit may operate to automatically determinethe adverse delivery condition based upon the intended deliverylocation, the first location of the mobile master node apparatus, andthe intended delivery time parameter (such as a delivery date, deliverytime, or range or dates and/or times that a shipping customer for theitem may deem appropriate).

While FIGS. 38 and 39 describe generating and/or transmitting correctivedelivery notifications, FIGS. 40-42 describe embodiments that generateand/or transmit corrective pickup notifications involving similarwireless node elements. Here, embodiments of different types of masternodes are described as interacting with other node devices as they senseadverse pickup conditions relative to an item and then generate and/ortransmit timely and useful corrective pickup notifications when, forexample, an item was not picked up or was picked up by an incorrectcourier master node by mistake. The exemplary corrective pickupnotifications provide for improvements where, for example, a costlysituation may be avoided when the item was incorrectly picked up and maybe heading out of a warehouse unexpectedly, but can be corrected priorto leaving the premises. In further embodiments, the notifications maybe provided to a shipping customer directly or indirectly with server100 operating as an intermediary system that forwards the relevantnotification to the shipping customer's server (e.g., where aninventory/warehouse module on that server may be notified and supplylevels and inventory counts may be adjusted).

FIG. 40 is a flow diagram illustrating an exemplary method forgenerating a corrective pickup notification related to an item beingshipped by a mobile master node based upon an identified intended pickupmaster node in accordance with an embodiment of the invention. Such amobile master node may be used by personnel involved in picking up theitem as part of managing and tracking the item for later delivery.Referring now to FIG. 40, method 4000 begins at step 4005 with themobile master node identifying a location of an ID node associated withthe item. At step 4010, method 4000 continues with determining, by themobile master node, whether the location of the ID node indicates theitem is accompanying the mobile master node as the mobile master nodemoves from a first location to a second location. For example, mobilecourier master node 3710 may determine whether the location of the IDnode indicates the item is accompanying the mobile master node as themobile master node moves from a first location to a second location(such as how item 3700 d now accompanies mobile courier master node 3710instead of being located at location 1). In a further embodiment ofmethod 4000, step 4010 may have location circuitry on the mobile masternode detecting a location of the mobile master node, and comparing thelocation of the mobile master node to the location of the ID node as themobile master node moves from the first location to the second locationto determine whether the item is accompanying the mobile master node.Such a comparison may provide an indication that the ID node isaccompanying the mobile master node when their relative locations overtime are relatively close, as opposed to increasingly different andfarther apart.

At step 4015, method 4000 continues with the mobile master nodereceiving shipping information related to the item. As noted in otherembodiments where shipping information related to the item may beprovided to a master node, the shipping information may be received, forexample, the ID node over a secure connection between the ID node andthe mobile master node. In another example, the shipping information maybe received from a server over a secure connection between the serverand the mobile master node. As such, utilizing a secure connection mayallow for an encrypted exchange of the shipping information to betterprotect such sensitive information and prevent spoofing issuespreviously noted when detecting signals from other nodes.

At step 4020, method 4000 continues with the mobile master nodeidentifying an intended pickup master node from the shippinginformation. In this embodiment, the shipping information may haveinformation on an anticipated transit path for the item and, as such,may have information on what mobile master node is intended to be taskedwith handling a pickup operation involving the item (e.g., where an IDnode associated with the item may become associated with the mobilemaster node and where personnel operating the mobile master node mayphysically obtain the item as temporary physical custody of the itemtransfers as a result of the pickup operation).

At step 4025, method 4000 proceeds where the mobile master nodeautomatically senses an adverse pickup condition related to the itembased upon the identified intended pickup master node and whether thelocation of the ID node indicates the item is accompanying the mobilemaster node. In more detail, the mobile master node may automaticallysense the adverse pickup condition related to the item when the intendedpickup master node does not correspond to the mobile master node and thelocation of the ID node indicates the item is accompanying the mobilemaster node. For example, if the intended pickup master node for item3700 d is not mobile courier master node 3710 and, as shown in FIG. 37C,item 3700 d is accompanying the mobile courier master node 3710, thenmaster node 3710 is operative to automatically sense there is a pickuprelated issue with item 3700 d (e.g., the master node 3710 picked up awrong item—namely, item 3700 d).

At step 4030, method 4000 has the mobile master node generating thecorrective pickup notification based upon the adverse pickup conditionsensed. Thus, the mobile master node, based upon assessing detected andreceived shipping information and making location measurements anddeterminations, may quickly identify a pickup issue with this particularitem and generate the corrective pickup notification accordingly.

In a further embodiment of method 400, step 4030 may have the mobilemaster node generating the corrective pickup notification by generatinga prompt on the mobile master node, the prompt being related to theadverse pickup condition. Such a prompt may comprise an alert soundgenerated by the mobile master node (e.g., using a speaker 3725 onmaster node 3710). In another embodiment, the prompt may compriseelectronic feedback on a user interface of the mobile master node (e.g.,using display 3730 on master node 3710). In more detail, such electronicfeedback may be different types of instructions. For example, theelectronic feedback may include an instruction not to deliver the itembased upon the sensed adverse pickup condition or an instruction toalter a current direction of movement or move to a specified location(such as a prior location of the mobile master node or an alternativelocation where the pickup issue may be resolved quickly and efficiently)based upon the sensed adverse pickup condition.

Those skilled in the art will appreciate that method 4000 as disclosedand explained above in various embodiments may be implemented using anexemplary mobile master node (such as exemplary master node 110 a asillustrated in FIG. 4 and mobile courier master node 3710 as illustratedin FIGS. 37A-C) running one or more parts of a control and managementcode (such as a delivery notification code module) to implement any ofthe above described functionality. Such code may be stored on anon-transitory computer-readable medium (such as memory storage 415 inan exemplary master node). Thus, when executing such code, a processingunit of the mobile master node (such as unit 400) may be operative toperform operations or steps from the exemplary methods disclosed above,including method 4000 and variations of that method.

Furthermore, an exemplary system for transmitting a corrective pickupnotification for a shipped item to a courier master node is shown inFIGS. 37A-37C. Those skilled in the art will appreciate that two or moreof the node elements shown in FIGS. 37A-37C and described above withrespect to method 4000 (and variations of that method) using anexemplary mobile master node apparatus may be deployed to implement suchsystem embodiments with the particular node elements (as describedabove) interacting in a manner to generate a corrective pickupnotification for a shipped item based upon an intended pickup masternode.

Where FIG. 40 explains aspects of an exemplary method for generating acorrective pickup notification from the perspective of a mobile masternode, FIGS. 41 and 42 explain aspects of exemplary methods fortransmitting an exemplary corrective pickup notification from theperspective of an exemplary master node at a particular location thatmay monitor nodes associated with items and locations of various othermaster nodes. In more detail, FIG. 41 is a flow diagram illustratingexemplary method 4100 that begins at step 4105 with a first master nodeat a first location receiving shipping information related to the item.More particularly, the shipping information may in some embodiments bereceived from an ID node associated with the item over a secureconnection between the ID node and the first master node. In otherembodiments, the shipping information may be received from a server overa secure connection between the server and the first master node.

At step 4110, method 4100 has the first master node parsing the shippinginformation to identify an intended pickup master node from the shippinginformation. In some embodiments, this may involve decrypting theshipping information or assessing a particular part of the shippinginformation related to the anticipated transit path of the item and,more specifically, to an anticipated master node that is next in a chainof associated custody related to the item.

At step 4115, method 4100 has the first master node identifying alocation of an ID node associated with the item. As described in moredetail herein, embodiments may have the first master node identifyingthe ID node's location by making use of one or more of the locatingtechniques described above.

At step 4120, method 4100 has the first master node determine whetherthe location of the ID node over a period of time indicates the item ismoving away from the first location. For example, as shown in FIGS. 37Band 37C, master node 3705 a may determine whether the location of node3720 d over time (e.g., such as the time taken to progress from thelocation shown in FIG. 37B to the location shown in FIG. 37C) indicatesitem 3700 d is moving away from location 1 (i.e., the location of masternode 3705 a).

At step 4125, method 4100 has the first master node identify a couriermaster node accompanying the ID node as the ID node moves away from thefirst location. For example, the master node 3705 a may identify thelocations of surrounding nodes, including those of ID node 3720 dassociated with item 3700 d and mobile courier master node 3710. Withsuch location information (that may be detected by master node 3705 aitself or via information provided by back-end server 100), master node3705 a may identify mobile courier master node 3710 has accompanying IDnode 3720 d as ID node 3720 d moves away from location 1 (i.e., thelocation of master node 3705 a).

At step 4130, method 4100 has the first master node automaticallysensing an adverse pickup condition related to the item when theidentified courier master node does not correspond to the intendedpickup master node and the location of the ID node over the period oftime indicates the item is moving away from the first location. In thissituation, the identified courier master node may have picked up theitem and its related ID node by mistake.

Thus, in response to sensing such an adverse pickup condition, method4100 continues to step 4135 where the first master node transmits acorrective pickup notification to a second device based upon the adversepickup condition sensed. In a further embodiment of method 4100, such asecond device may include a server, the identified courier master node,a node device associated with a customer shipping the item (such as acustomer's mobile user access device operating as a node), or a nodedevice associated a recipient of the item (such as the recipient'ssmartphone operating as a node).

The corrective pickup notification may identify the item as being awrong pickup and present one or more electronic instructions on what todo with the wrong pickup item or where to move, such as the location ofthe first master node or some other specified location. This may allowfor timelier drop off where the item was picked up by mistake to allowfor appropriate delivery of the item.

Those skilled in the art will appreciate that method 4100 as disclosedand explained above in various embodiments may be implemented using anexemplary master node (such as exemplary master node 110 a asillustrated in FIG. 4 and master nodes 3705 a and 3705 b as illustratedin FIGS. 37A-C) running one or more parts of a control and managementcode (such as a delivery notification code module) to implement any ofthe above described functionality. Such code may be stored on anon-transitory computer-readable medium (such as memory storage 415 inan exemplary master node). Thus, when executing such code, a processingunit of the mobile master node (such as unit 400) may be operative toperform operations or steps from the exemplary methods disclosed above,including method 4100 and variations of that method.

Additionally, a system embodiment may leverage such an exemplary masternode at the location in conjunction with a server and other nodesdescribed above that may receive such valued corrective pickupnotifications that help improve and enhance a monitored pickup anddelivery operation related to the item.

FIG. 42 is a flow diagram illustrating an alternative exemplary methodfor transmitting a corrective pickup notification related to an item bya master node associated with a location in accordance with anembodiment of the invention. Referring now to FIG. 42, method 4200begins at step 4205 with the first master node at a first locationreceiving shipping information related to the item. As with the priorembodiment, the shipping information may be received from the ID nodeover a secure connection between the ID node and the first master node.In another embodiment, the shipping information may be received from aserver over a secure connection between the server and the first masternode.

At step 4210, method 4200 proceeds with the first master nodeidentifying an intended pickup master node from the shipping informationin similar fashion as discussed above in step 4110. Method 4200 proceedsfrom step 4210 to step 4215 where the first master node detects whethera location of the ID node over a period of time indicates the item isnot moving away from the first location over the period of time. In moredetail, the first master node may track the location of the ID node overa period of time to determine if the ID node and the item with which itis associated are moving and whether such movement is in a directionaway from the first master node. At step 4220, method 4200 proceeds withthe first master node determining a location of the intended pickupmaster node over the same period of time. In this manner, the firstmaster node is able to track and monitor the respective locations of theitem through its associated ID node and the intended pickup master node.Armed with this detected information, method 4200 has the first masternode automatically sense an adverse pickup condition related to the itemwhen the intended pickup master node is determined to be moving awayfrom the first location while the location of the ID node over theperiod of time indicates the item is not moving away from the firstlocation.

As a result, at step 4230, method 4200 proceeds with the first masternode transmitting the corrective pickup notification to a second devicebased upon the adverse pickup condition sensed. In more detail, thesecond device may comprise a server so that the server stays informed ofthe such an adverse pickup condition for the particular item; theintended pickup master node noting that the intended pickup master nodemissed picking up the item; a node device associated with a shipper ofthe item to keep the shipper aware of at least a delayed pickup of theitem; and a node device associated a recipient of the item to update therecipient about a potential delay.

In a further embodiment of method 4200, the corrective pickupnotification transmitted to the intended pickup master node may identifythe item as being not being picked up and, further, may include aninstruction to move to a specified location (such as the location of thefirst master node to allow for appropriate pickup of the item) or to analternative location where, for example, the item may be found for asecond opportunity at pickup of the item.

Those skilled in the art will appreciate that method 4200 as disclosedand explained above in various embodiments may be implemented using anexemplary master node (such as exemplary master node 110 a asillustrated in FIG. 4 and master nodes 3705 a and 3705 b as illustratedin FIGS. 37A-C) running one or more parts of a control and managementcode (such as a delivery notification code module) to implement any ofthe above described functionality. Such code may be stored on anon-transitory computer-readable medium (such as memory storage 415 inan exemplary master node). Thus, when executing such code, a processingunit of the mobile master node (such as unit 400) may be operative toperform operations or steps from the exemplary methods disclosed above,including method 4200 and variations of that method.

Generating Inventory Item Pickup Notifications

The notifications generated and/or transmitted in the above describeddelivery/pickup embodiments are typically used with an item beingshipped or that has entered a shipment operation were the item may be onits transit path from an origin to a destination (with one or morehand-off management events along the way as described above with respectto FIG. 17). Further embodiments may leverage elements of a wirelessnode network when applied in an inventory control type of embodiment andwhere it may be desired to automatically generate a type of notificationwhen an item may be improperly leaving a particular location, such as astorage facility (e.g., a warehouse that may temporarily house andmaintain one or more different types of items). In general, such anembodiment may have a master node associated with the facility orlocation. The master node may operate to monitor inventory in thefacility or location and generate notifications when an inventory itemis not authorized to leave the facility.

FIGS. 43A and 43B are diagrams illustrating an exemplary master nodeassociated with a fixed location that generates a pickup notificationrelated to an inventory item in accordance with an embodiment of theinvention. Referring now to FIG. 43A, server 4300 (referred to as anexemplary inventory control server in some embodiments) is shownconnected to master node 4305 via network 105. In the illustratedembodiment, exemplary master node 4305 is deployed as being associatedwith a particular location 4350 where an inventory of items 4310 a-4310n are maintained. In a more detailed embodiment, location 4305 may be astorage facility or, more specifically, a warehouse. As such, masternode 4305 may be associated with location 4305 by being fixed relativeto location 4305 or, in some instances, deployed relative to location4305 but in a non-fixed manner while still being associated with thelocation. For example, exemplary master node 4305 may be a warehousemaster node as shown in FIGS. 43A and 43B and disposed in a convenientposition that allows for communication with items 4310 a-4310 n whilemaintained within the inventor. Depending on the density of thewarehouse, an embodiment of such a master node may be responsible forall or only a portion of the warehouse location or different storageareas within the warehouse location. In another example, exemplarymaster node 4305 may be a mobile master node that may move throughout aparticular location (such as a mobile master node disposed on anautonomous mobile vehicle that moves as the mobile master node monitorsID nodes associated with inventory items within location 4350).

As shown in FIG. 43A, exemplary master node 4305 may periodicallymonitor ID nodes 4320 a-4320 n respectively associated with inventoryitems 4310 a-4310 n within location 4350. This monitoring may involvegathering and/or generating relevant information from or about therespective ID nodes (such as shared data 445, sensor data 450, locationdata 455, and the like). As an inventory item may be moved withinlocation 4350, master node 4305 is operative to track the inventory itemvia its associated ID node. If an inventory item is authorized to bereleased from location 4350, server 4300 may provide release informationto master node 4305 reflecting a level of authorization that includesthe particular inventory item (such as a category of items/nodes thatmay be released or a particular item(s) or ID node(s) authorized forrelease). Thus, the release information provided by server 4300essentially provides an approval for one or more inventory items toleave the location 4350 (e.g., leave a warehouse and transition from andinventory item to an item being shipped).

As shown in FIG. 43B, item 4310 n is detected by master node 4305 asmoving in a direction away from location 4350. Based upon the currentrelease information provided from server 4300 and the detectedlocation/direction of movement of item 4310 n (via interactions withrelated node 4320 n), master node 4305 may generated a pickupnotification relative to item 4310 n. Such a pickup notification mayprovide the basis for the master node 4305 to issue, provide, ortransmit an alert related to item 4310 n as described in more detailbelow with reference to FIG. 44.

FIG. 44 is a flow diagram illustrating an exemplary method forgenerating a pickup notification related to an inventory item using anexemplary master node associated with a fixed location in accordancewith an embodiment of the invention. Referring now to FIG. 44, method4400 begins at step 4405 with the master node associated with the fixedlocation monitoring a location of an ID node associated with theinventory item. For example, in the embodiment of FIGS. 43A and 43B,exemplary master node 4305 is associated with location 4350, which maybe a fixed location (such as a storage facility or, more specifically, awarehouse).

At step 4410, method 4400 proceeds with the master node receivingrelease information from an inventory control server operative tocommunicate with the master node. For example, server 4300 shown inFIGS. 43A and 43B may have transmitted a message to master node 4305having release information on what may be authorized to leave location4350. Such release information may, in some examples, identify acategory for inventory release (such as a category of inventory itemsthat are authorized for release or a category of ID nodes that areauthorized for release). In another example, the release information mayidentify one or more specific authorized released nodes (such as one ormore of the ID nodes associated with inventory items maintained withlocation 4350).

At step 4415, method 4400 proceeds with the master node detectingmovement of the ID node relative to the fixed location. The master nodemay implement detecting movement by locating the ID node using one ormore of the location determination techniques described herein. As such,and determining the ID node's location over time, the master node maydetect movement of the ID node relative to the fixed location.

At step 4420, method 4400 proceeds with the master node generating apickup notification for the inventory item based upon the releaseinformation and the detected movement of the ID node. Armed with therelease information from the server and the detected movement of theparticular ID node associated with the inventor item, the master nodemay automatically and efficiently leverage its ability to locate andtrack nodes, and generate such a pickup notification. In a furtherembodiment of method 4400, when the release information identifies acategory for inventory release, the master node may generate the pickupnotification for the inventory item in step 4420 when the detectedmovement of the ID node reflects movement away from the fixed locationand the category for inventory release does not correspond to theinventory item (or, in another embodiment, the ID node associated withthe inventory item). In such a situation, the inventory item may not beauthorized for release and the pickup notification functions as anautomatic type of alert that leverages the hierarchy of the ID node, themaster node, and the server aspects of the wireless node network (suchas shown in FIGS. 43A and 43B).

In another embodiment of method 4400, when the release informationcomprises at least one authorized released node, the master node maygenerate the pickup notification for the inventory item in step 4420when the detected movement of the ID node reflects movement away fromthe fixed location and indicated authorized released node(s) from therelease information does not include the ID node associated with theinventory item.

In these embodiments, the pickup notification may be generated prior tothe inventory item leaving the location. However, in another embodimentof method 4400, step 4420 may have the master node generating the pickupnotification for the inventory item when the master node detects alocation of the ID node as being beyond a threshold distance away fromthe fixed location of the master node and the release informationreceived by the master node does not authorize the ID node to leave thestorage facility. For example, as shown in FIG. 43B, item 4310 n and itsassociated node 4320 n are located outside of location 4350. Should thelocation of node 4320 n be determined as beyond a threshold distanceaway from location 4350, item 4310 n and its associated node 4320 n maybe considered to have been picked up and outside of location 4350without authorization. An exemplary threshold distance may be set for aparticular implementation considering how difficult locating an ID nodeis by a facility master node. Other embodiments may dynamically adjustthe threshold distance based upon the contextual environment of the IDnode and/or the master node (e.g., where certain access entrances tolocation 4350 have a more robust communication environment due tosurrounding structure and potential other radio interference sources orshielding structure when compares other entrances which may beassociated with more difficult communication environments).

In a further embodiment, method 4400 may also have the master nodeprovide the pickup notification on a user interface of the master node.As such, the pickup notification as provided via the user interface(e.g., electronic feedback information shown on a display, audioinformation provided through a speaker, etc.) may indicate the inventoryitem has been improperly moved (such as improper removal of theinventory item from a storage facility at the location 4350) and allowfor corrective action to be initiated.

At step 4425, method 4400 may proceed in some embodiments with themaster node transmitting an alert to the inventory control server (or asecond node device—such as another master node, or a mobile user accessdevice operating as a node). The transmitted alert relates to the pickupnotification and may indicate the inventory item has been improperlymoved, and more specifically, may also provide a corrective actionrelative to the detected movement of the ID node relative to the fixedlocation.

At step 4430, method 4400 may also proceed in some embodiments with themaster node updating inventory control information related to theinventory level of items when the detected movement of the ID nodereflects movement of the ID node away from the fixed location and the IDnode is authorized to leave the storage facility consistent with therelease information. At step 4435, method 4400 may conclude by havingthe master node transmitting the updated inventory control informationto the inventory control server so that the inventory control server maymaintain current inventory data relative to the inventory kept atlocation 4350. For example, server 4300 may receive such updatedinventory control information from master node 4305 and maintain suchinformation within memory on or operatively accessible to server 430(such as memory 520, 525 of exemplary server 100 or a separate databasemaintained by server 4300 with inventory control information relative tolocation 4350 and other locations).

Those skilled in the art will appreciate that method 4400 as disclosedand explained above in various embodiments may be implemented using anexemplary master node (such as exemplary master node 110 a asillustrated in FIG. 4 and master node 4305 as illustrated in FIGS.43A-43B) running one or more parts of a control and management code(such as a pickup notification code module) to implement any of theabove described functionality. Such code may be stored on anon-transitory computer-readable medium (such as memory storage 415 inan exemplary master node). Thus, when executing such code, a processingunit of the mobile master node (such as unit 400) may be operative toperform operations or steps from the exemplary methods disclosed above,including method 4400 and variations of that method.

A further embodiment of exemplary master node apparatus for generating apickup notification related to an inventory is set forth in Exhibit 6 isconsistent with the above described exemplary master node as explainedwith reference to method 4400 (and variations of that method).

In still a further embodiment, an exemplary system is disclosed forgenerating a pickup notification related to an inventory item as setforth in Exhibit 6 that generally comprises an exemplary inventorycontrol server operating in conjunction with a master node associatedwith a fixed location (also consistent with the above exemplary masternode as explained with reference to method 4400 (and variations of thatmethod)). As noted in the system embodiment explained in Exhibit 6, themaster node is operative to generate a pickup notification as well astransmit different types of alerts to the inventory control server,which is operative to interact with the master node as set forth.

It should be emphasized that the sequence of operations to perform anyof the methods and variations of the methods described in theembodiments herein are merely exemplary, and that a variety of sequencesof operations may be followed while still being true and in accordancewith the principles of the present invention.

At least some portions of exemplary embodiments outlined above may beused in association with portions of other exemplary embodiments tobetter manage and locate nodes in a wireless node network or use suchnodes and network elements as part of a hierarchical node network thatprovides particular enhancements and improvements to technicalprocesses, such as logistics monitoring operations. For example, some ofthe exemplary embodiments involve steps that involve locating a node(such as an ID node, a master node, or a mobile user access deviceoperating as a type of node that interacts with other node elements inthe described embodiment of an wireless node network of devices). Thevarious exemplary techniques described herein for locating a node may bedeployed in such embodiments. In another example, the various exampleembodiments involving node associations may be used in conjunction withvarious other embodiments (such as deploying different types ofestablished and tracked association relationships between a node and asecond entity (e.g., another node, a person, an object, a facility, apiece of equipment)). Thus, those skilled in the art will appreciatethat at least some of the exemplary embodiments disclosed herein may beused independently from one another and/or in combination with oneanother and may have applications to devices and methods not disclosedherein.

Those skilled in the art will appreciate that embodiments may provideone or more advantages, and not all embodiments necessarily provide allor more than one particular advantage as set forth here. Additionally,it will be apparent to those skilled in the art that variousmodifications and variations can be made to the structures andmethodologies described herein. Thus, it should be understood that theinvention is not limited to the subject matter discussed in thedescription. Rather, the present invention is intended to covermodifications and variations.

FURTHER PARTICULAR EMBODIMENTS

What follows below is a listing of exemplary sets of particularembodiments focusing on one or more aspects of the different embodimentsdescribed above. Each of the different sets of particular embodimentsrespectively effect improvements to the technology of electronics-basedenhanced delivery and/or pickup management of a shipped item using oneor more elements of a logistics-centered wireless node network as itrelates to selective release of the shipped item, correctivedelivery/pickup notifications for the shipped item, and pickupnotifications related to an inventory item. As such, within each furtherembodiment heading are numbered aspects describing a specifictechnological application of one or more nodes in such a wireless nodenetwork that improve or otherwise enhance these technical fields, asexplicitly explained and supported by the disclosure above. Eachnumbered aspect appearing below a particular heading may make referenceto other numbered aspects that appear below that particular heading in adependent relationship.

Further Embodiment A Improved Methods, Apparatus, and Systems forGenerating a Corrective Pickup Notification for a Shipped Item Using aMobile Master Node

1. An improved method for generating a corrective delivery notificationrelated to an item, the method comprising: identifying, by a mobilemaster node involved with a delivery of the item, an intended deliverylocation related to the item; detecting, by location circuitry withinthe mobile master node, a current location of the mobile master node;automatically sensing, by the mobile master node, an adverse deliverycondition related to the item based upon the intended delivery locationand the current location of the mobile master node; and generating, bythe mobile master node, the corrective delivery notification based uponthe adverse delivery condition sensed.

2. The method of embodiment 1, wherein the step of automatically sensingfurther comprises automatically sensing, by the mobile master node, theadverse delivery condition as an incorrect location for delivery of theitem based upon a comparison of the identified intended deliverylocation and the detected current location of the mobile master node.

3. The method of embodiment 2, wherein the step of automatically sensingthe incorrect location further comprises comparing the current locationof the mobile master node to a proximity distance threshold related tothe identified intended delivery location.

4. The method of embodiment 1, wherein the step of automatically sensingfurther comprises automatically sensing, by the mobile master node, theadverse delivery condition as a movement away from the intended deliverylocation based upon the identified intended delivery location and thedetected current location of the mobile master node.

5. The method of embodiment 4, wherein the step of automatically sensingfurther comprises: determining, by the mobile master node, a movementdirection associated with the mobile master node; comparing, by themobile master node, the determined movement direction and the detectedcurrent location of the mobile master node relative to the intendeddelivery location; and identifying the adverse delivery condition aswhether the mobile master node is moving away from the intended deliverylocation based upon the comparing step.

6. The method of embodiment 1, wherein the identifying step furthercomprises:

detecting, by the mobile master node, a signal broadcast from an ID nodeassociated with the item;

accessing, by the mobile master node, shipping information within thedetected signal, wherein the shipping information is related to thedelivery of the item; and

identifying the intended delivery location from the shippinginformation.

7. The method of embodiment 1 further comprising establishing a secureconnection from the mobile master node to the ID node associated withthe item.

8. The method of embodiment 7, wherein the secure connection comprisesan encrypted exchange of the shipping information from the ID node tothe mobile master node.

9. The method of embodiment 1, wherein the identifying step furthercomprises: receiving, by the mobile master node, shipping informationfrom a server; and identifying the intended delivery location from thereceived shipping information.

10. The method of embodiment 9, wherein the receiving step furthercomprises receiving, by the mobile master node, the shipping informationfrom the server over a secure connection between the mobile master nodeand the server.

11. The method of embodiment 9 further comprising the step oftransmitting a shipping information request to the server by the mobilemaster node, wherein the shipping information received by the mobilemaster node is provided by the server in response to the shippinginformation request and over a secure communication connection betweenthe mobile master node and the server.

12. The method of embodiment 1 further comprising the step of receiving,by the mobile master node, an intended delivery time parameter relatedto the item as part of shipping information related to the delivery ofthe item; and wherein the adverse delivery condition is further basedupon the intended delivery time parameter.

13. The method of embodiment 12, wherein the intended delivery timeparameter is provided by a server over a secure communication connectionbetween the mobile master node and the server, wherein the intendeddelivery time comprises at least one from a group consisting of adelivery deadline and a delivery time range.

14. The method of embodiment 12, wherein the intended delivery timeparameter is provided by an ID node associated with the item over asecure communication connection between the mobile master node and theID node, wherein the intended delivery time comprises at least one froma group consisting of a delivery deadline and a delivery time range.

15. The method of embodiment 1, wherein the mobile master node isassociated with a courier involved with the delivery of the item.

16. The method of embodiment 15, wherein the step of generating thecorrective delivery notification further comprises automaticallyprompting the courier with the corrective delivery notification.

17. The method of embodiment 16, wherein the step of automaticallyprompting further comprises generating an alert sound by the mobilemaster node.

18. The method of embodiment 16, wherein the step of automaticallyprompting further comprises generating electronic feedback for thecourier on a user interface of the mobile master node.

19. The method of embodiment 18, wherein the step of generating theelectronic feedback for the courier on the user interface furthercomprises generating a display on the user interface, wherein thedisplay includes at least an instruction not to deliver the item basedupon the adverse delivery condition.

20. The method of embodiment 18, wherein the step of generating theelectronic feedback for the courier on the user interface furthercomprises generating a display on the user interface, wherein thedisplay includes at least an instruction to alter a current direction ofmovement based upon the adverse delivery condition.

21. The method of embodiment 20, wherein the instruction to alter thecurrent direction of movement comprises an instruction to move to aspecified location.

22. The method of embodiment 21, wherein the specified locationcomprises a prior location of the mobile master node.

23. A mobile master node apparatus involved with a delivery of an item,the apparatus comprising: a node processing unit; a node memory storagecoupled to the node processing unit, the node memory storage maintainingdelivery notification code for execution by the node processing unit;location circuitry coupled to the node processing unit, the locationcircuitry being operative to detect a location of the mobile master nodeapparatus; a communication interface coupled to the node processing unitand operative to access a wireless communication path; and wherein thenode processing unit, when executing the delivery notification codemaintained on the node memory storage, is operative to identify anintended delivery location associated with the item from shippinginformation related to the item, cause the location circuitry to detecta current location of the mobile master node; automatically determine anadverse delivery condition related to the item based upon the intendeddelivery location and the detected current location of the mobile masternode, and generate a corrective delivery notification based upon thedetermined adverse delivery condition related to the item.

24. The mobile master node apparatus of embodiment 23, wherein the nodememory storage maintains the shipping information related to the item.

25. The mobile master node apparatus of embodiment 24, wherein theshipping information comprises an intended delivery time parameterrelated to the item; and wherein the node processing unit is operativeto automatically determine the adverse delivery condition based upon theintended delivery location, the detected current location of the mobilemaster node, and the intended delivery time parameter.

26 The mobile master node apparatus of embodiment 25, wherein theintended delivery time parameter comprises at least one from a groupconsisting of a delivery deadline and a delivery time range.

27. The mobile master node apparatus of embodiment 24, wherein the nodeprocessing unit is further operative to receive the shipping informationrelated to the item from a second node.

28. The mobile master node apparatus of embodiment 27, wherein the nodeprocessing unit is operative to receive the shipping information over asecure connection established between the second node and thecommunication interface of the mobile master node apparatus.

29. The mobile master node apparatus of embodiment 28, wherein thesecure connection comprises an encrypted exchange of the shippinginformation from the second node to the node processing unit via thecommunication interface.

30. The mobile master node apparatus of embodiment 27, wherein thesecond node comprises an ID node associated with the item and is inoperative communication with the mobile master node apparatus over thecommunication interface.

31. The mobile master node apparatus of embodiment 30, wherein the nodeprocessing unit is further operative to identify the shippinginformation from at least a portion of an identification signalbroadcast from the ID node, and determine the intended deliver locationfrom the shipping information.

32. The mobile master node apparatus of embodiment 27, wherein thesecond node comprises a server in operative communication with themobile master node apparatus over the communication interface.

33. The mobile master node apparatus of embodiment 23, wherein the nodeprocessing unit is operative to automatically determine the adversedelivery condition by being further operative to automatically sense theadverse delivery condition as an incorrect location for delivery of theitem based upon a comparison of the identified intended deliverylocation and the detected current location of the mobile master nodeapparatus.

34. The mobile master node apparatus of embodiment 33, wherein the nodeprocessing unit is operative to automatically sense the incorrectlocation by being further operative to compare the current location ofthe mobile master node apparatus to a proximity distance thresholdrelated to the identified intended delivery location.

35. The mobile master node apparatus of embodiment 23, wherein the nodeprocessing unit is operative to automatically determine the adversedelivery condition by being further operative to automatically sense theadverse delivery condition as a movement of the mobile master nodeapparatus away from the intended delivery location based upon theidentified intended delivery location and the detected current locationof the mobile master node apparatus.

36. The mobile master node apparatus of embodiment 35, wherein the nodeprocessing unit interacts with the location circuitry to determine amovement direction associated with the mobile master node apparatus overa period of time; and wherein the node processing unit is operative toautomatically sense movement of the mobile master node apparatus awayfrom the intended delivery location based upon a comparison of thedetermined movement direction and the detected current location of themobile master node relative to the intended delivery location.

37. The mobile master node apparatus of embodiment 23, wherein themobile master node apparatus is associated with a courier involved withthe delivery of the item.

38. The mobile master node apparatus of embodiment 37, wherein the nodeprocessing unit is operative to generate the corrective deliverynotification by being further operative to automatically prompt thecourier with the corrective delivery notification.

39. The mobile master node apparatus of embodiment 38 further comprisinga speaker operatively coupled to the node processing unit; and whereinthe node processing unit is operative to automatically prompt thecourier with the corrective delivery notification by being furtheroperative to generate an alert sound on the speaker.

40. The mobile master node apparatus of embodiment 38, furthercomprising a user interface operatively coupled to the node processingunit; and wherein the node processing unit is operative to automaticallyprompt the courier with the corrective delivery notification by beingfurther operative to generate electronic feedback for the courier on theuser interface of the mobile master node apparatus.

41. The mobile master node apparatus of embodiment 40, wherein theelectronic feedback for the courier on the user interface furthercomprises a display on the user interface including at least aninstruction not to deliver the item based upon the adverse deliverycondition.

42. The mobile master node apparatus of embodiment 40, wherein theelectronic feedback for the courier on the user interface furthercomprises a display on the user interface including at least aninstruction to alter a current direction of movement based upon theadverse delivery condition.

43. The mobile master node apparatus of embodiment 42, wherein theinstruction to alter the current direction of movement comprises aninstruction to move to a specified location.

44. The mobile master node apparatus of embodiment 43, wherein thespecified location comprises a prior location of the mobile master node.

Further Embodiment B Improved Methods, Apparatus, and Systems forTransmitting a Corrective Pickup Notification for a Shipped Item to aCourier Master Node

1. An improved method for transmitting a corrective deliverynotification related to an item, the method comprising: receiving, by afirst master node at a first location, shipping information related tothe item; parsing the received shipping information, by the first masternode, to identify an intended delivery location related to the item;automatically sensing, by the first master node, an adverse deliverycondition related to the item based upon the first location of firstmaster node and the intended delivery location for the item; andtransmitting, by the first master node, the corrective deliverynotification to a courier master node based upon the adverse deliverycondition sensed by the first master node.

2. The method of embodiment 1, wherein the step of automatically sensingfurther comprises determining, by the first master node, a differencebetween the first location and the intended delivery location for theitem when an ID node associated with the item arrives at the firstlocation, wherein the determined difference indicates an incorrectlocation for delivery of the item as the adverse delivery condition.

3. The method of embodiment 1, wherein the step of automatically sensingfurther comprises: determining, by the first master node, the firstlocation does not correspond to the intended delivery location for theitem; and detecting, by the first master node, when an ID nodeassociated with the item is proximate and stationary relative to thefirst master node when the courier master node is moving away from thefirst location, wherein the detected stationary location of the ID nodeindicating an incorrect location for delivery of the item as the adversedelivery condition.

4. The method of embodiment 1, wherein the step of automatically sensingfurther comprises detecting, by the first mobile master node, a movementof an ID node associated with the item away from the first location asthe adverse delivery condition when the first location corresponds tothe intended delivery location.

5. The method of embodiment 1, wherein the receiving step furthercomprises receiving, by the first master node, the shipping informationas part of a broadcasted signal from an ID node associated with theitem.

6. The method of embodiment 1 further comprising establishing a secureconnection from the first master node to the ID node associated with theitem.

7. The method of embodiment 6, wherein the secure connection comprisesan encrypted exchange of the shipping information from the ID node tothe first master node.

8. The method of embodiment 1, wherein the receiving step furthercomprises receiving, by the first master node, the shipping informationas part of a preloading message from a server in communication with thefirst master node.

9. The method of embodiment 1, wherein the receiving step furthercomprises receiving, by the first master node, the shipping informationas a response from a server to a shipping information request from thefirst master node.

10. The method of embodiment 1, wherein the receiving step furthercomprises receiving, by the first master node, the shipping informationa server over a secure connection between the first master node and theserver.

11. The method of embodiment 1, wherein the shipping information furthercomprises an intended delivery time parameter related to delivery of theitem; and

wherein the adverse delivery condition is further based upon theintended delivery time parameter.

12. The method of embodiment 1, wherein the corrective deliverynotification to the courier master node identifies the item as being atan incorrect location for delivery.

13. The method of embodiment 12, wherein the corrective deliverynotification to the courier master node includes at least an instructionnot to deliver the item to the first location of the first master node.

14. The method of embodiment 1, wherein the corrective deliverynotification to the courier master node identifies the item as not beingdelivered to the intended delivery location.

15. The method of embodiment 14, wherein the corrective deliverynotification to the courier master node includes at least an instructionto move to a specified location.

16. The method of embodiment 15, wherein the specified locationcomprises the first location of the first master node to allow forappropriate delivery of the item.

17. A master node apparatus disposed at a first location and incommunication with a courier master node, the apparatus comprising: anode processing unit; a node memory storage coupled to the nodeprocessing unit, the node memory storage maintaining deliverynotification code for execution by the node processing unit; locationcircuitry coupled to the node processing unit, the location circuitrybeing operative to detect a current location of the master nodeapparatus; a communication interface coupled to the node processing unitand operative to access a wireless communication path; and

wherein the node processing unit, when executing the deliverynotification code maintained on the node memory storage, is operative toreceive shipping information via the communication interface, theshipping information being related to the item, store the receivedshipping information in the node memory storage, parse the receivedshipping information to identify an intended delivery location for theitem, cause the location circuitry to detect the current location of themaster node apparatus as the first location, automatically sense anadverse delivery condition related to the item based upon the firstlocation of the master node apparatus and the intended delivery locationfor the item, and cause the communication interface to transmit acorrective delivery notification to the courier master node based uponthe adverse delivery condition.

18. The master node apparatus of embodiment 17, wherein the nodeprocessing unit is operative to automatically sense the adverse deliverycondition by being further operative to determine a difference betweenthe first location of the master node apparatus and the intendeddelivery location for the item when an ID node associated with the itemarrives at the first location, wherein the determined differenceindicates an incorrect location for delivery of the item as the adversedelivery condition.

19. The master node apparatus of embodiment 17, wherein the nodeprocessing unit is operative to automatically sense the adverse deliverycondition by being further operative to: compare the detected currentlocation of the master node apparatus to the intended delivery locationto determine if the first location does not correspond to the intendeddelivery location for the item; detect that an ID node associated withthe item is proximate and stationary relative to the master nodeapparatus while detecting that the courier master node is moving awayfrom the first location; and determine the ID node is in an incorrectlocation for delivery of the item as the adverse delivery condition whenthe first location does not correspond to the intended delivery locationfor the item and the ID node is detected to be proximate and stationaryrelative to the master node apparatus while the courier master node isdetected to be moving away from the first location.

20. The master node apparatus of embodiment 17, wherein the nodeprocessing unit is operative to automatically sense the adverse deliverycondition by being further operative to detect a movement of an ID nodeassociated with the item away from the first location as the adversedelivery condition when the first location corresponds to the intendeddelivery location.

21. The master node apparatus of embodiment 17, wherein the correctivedelivery notification to the courier master node identifies the item asbeing at an incorrect location for delivery.

22. The master node apparatus of embodiment 21, wherein the correctivedelivery notification to the courier master node includes at least aninstruction not to deliver the item to the first location of the masternode apparatus.

23. The master node apparatus of embodiment 17, wherein the correctivedelivery notification to the courier master node identifies the item asnot being delivered to the intended delivery location.

24. The master node apparatus of embodiment 23, wherein the correctivedelivery notification to the courier master node includes at least aninstruction to move to a specified location.

25. The master node apparatus of embodiment 24, wherein the specifiedlocation comprises the location of the master node apparatus to allowfor appropriate delivery of the item.

26. The master node apparatus of embodiment 17, wherein the nodeprocessing unit is further operative to receive the shipping informationover the communication interface from an ID node associated with theitem, the ID node providing the shipping information over a secureconnection established over the wireless communication path as part of abroadcasted signal from the ID node, the secure connection being betweenthe ID node and the communication interface.

27. The master node apparatus of embodiment 17, wherein the nodeprocessing unit is further operative to receive the shipping informationover the communication interface from a server, the server apparatusproviding the shipping information over a secure connection between thecommunication interface and the server in a preloading message from theserver.

28. The master node apparatus of embodiment 27, wherein the serverapparatus providing the shipping information in response to a shippinginformation request transmitted by the communication interface to theserver.

29. The master node apparatus of embodiment 17, wherein the shippinginformation comprises an intended delivery time parameter related to theitem; and wherein the node processing unit is operative to automaticallydetermine the adverse delivery condition based upon the intendeddelivery location, the first location of the mobile master nodeapparatus, and the intended delivery time parameter.

Further Embodiment D Improved Methods, Apparatus, and Systems forTransmitting a Corrective Pickup Notification for a Shipped ItemAccompanying an ID Node Moving with a Courier Away from a Master Node

1. An improved method for transmitting a corrective pickup notificationrelated to an item being shipped, the method comprising: receiving, by afirst master node at a first location, shipping information related tothe item; identifying, by the first master node, an intended pickupmaster node from the shipping information; identifying, by the firstmaster node, a location of an ID node associated with the item;determining, by the first master node, whether the location of the IDnode over a period of time indicates the item is moving away from thefirst location; identifying, by the first master node, a courier masternode accompanying the ID node as the ID node moves away from the firstlocation; automatically sensing, by the mobile master node, an adversepickup condition related to the item when the identified courier masternode does not correspond to the intended pickup master node and thelocation of the ID node over the period of time indicates the item ismoving away from the first location; and transmitting, by the firstmaster node to a second logistics device, the corrective pickupnotification based upon the adverse pickup condition sensed.

2. The method of embodiment 1, wherein the shipping information isreceived from the ID node over a secure connection between the ID nodeand the first master node.

3. The method of embodiment 1, wherein the shipping information isreceived from a server over a secure connection between the server andthe first master node.

4. The method of embodiment 1, wherein the second logistics devicecomprises at least one from a group consisting of a server, theidentified courier master node, a third node device associated with acustomer shipping the item, and a fourth node device associated arecipient of the item.

5. The method of embodiment 1, wherein the corrective pickupnotification to the identified courier master node identifies the itemas being a wrong pickup.

6. The method of embodiment 5, wherein the corrective deliverynotification to the identified courier master node includes at least aninstruction to move to a specified location.

7. The method of embodiment 6, wherein the specified location comprisesthe first location of the first master node to allow for appropriatedelivery of the item.

Further Embodiment E Improved Methods, Apparatus, and Systems forTransmitting a Corrective Pickup Notification for a Shipped ItemAccompanying an ID Node Based Upon Intended Pickup Master Node Movement

1. An improved method for transmitting a corrective pickup notificationrelated to an item, the method comprising: receiving, by a first masternode at a first location, shipping information related to the item;identifying, by the first master node, an intended pickup master nodefrom the shipping information; detecting, by the first master node,whether a location of the ID node over a period of time indicates theitem is not moving away from the first location over the period of time;determining, by the first master node, a location of the intended pickupmaster node over the period of time; automatically sensing, by the firstmaster node, an adverse pickup condition related to the item when theintended pickup master node is moving away from the first location whilethe location of the ID node over the period of time indicates the itemis not moving away from the first location; and transmitting, by thefirst master node, the corrective pickup notification to a second devicebased upon the adverse pickup condition sensed.

2. The method of embodiment 1, wherein the shipping information isreceived from the ID node over a secure connection between the ID nodeand the first master node.

3. The method of embodiment 1, wherein the shipping information isreceived from a server over a secure connection between the server andthe first master node.

4. The method of embodiment 1, wherein the second device comprises atleast one from a group consisting of a server, the intended pickupmaster node, a third node device associated with a shipper of the item,and a fourth node device associated a recipient of the item.

5. The method of embodiment 1, wherein the corrective pickupnotification to the intended pickup master node identifies the item asbeing not being picked up.

6. The method of embodiment 5, wherein the corrective pickupnotification to the intended pickup master node includes at least aninstruction to move to a specified location.

7. The method of embodiment 6, wherein the specified location comprisesthe first location of the first master node to allow for appropriatepickup of the item.

Further Embodiment F Improved Methods, Apparatus, and Systems forGenerating a Pickup Notification Related to an Inventory Item

1. An improved method for generating a pickup notification related to aninventory item using a master node associated with a fixed location, themethod comprising: monitoring, by the master node, a location of an IDnode associated with the inventory item; receiving, by the master node,release information from an inventory control server operative tocommunicate with the master node; detecting, by the master node,movement of the ID node relative to the fixed location; and generating,by the master node, the pickup notification for the inventory item basedupon the release information and the detected movement of the ID node.

2. The method of embodiment 1, wherein the release informationidentifies a category for inventory release; and wherein the generatingstep further comprises generating the pickup notification for theinventory item when (a) the detected movement of the ID node reflectsmovement of the ID node away from the fixed location and (b) thecategory for inventory release does not correspond to the inventoryitem.

3. The method of embodiment 1, wherein the release informationidentifies a category for inventory release; and wherein the generatingstep further comprises generating the pickup notification for theinventory item when (a) the detected movement of the ID node reflectsmovement of the ID node away from the fixed location and (b) thecategory for inventory release does not correspond to the ID nodeassociated with the inventory item.

4. The method of embodiment 1, wherein the release information comprisesat least one authorized released node; and wherein the generating stepfurther comprises generating the pickup notification for the inventoryitem when (a) the detected movement of the ID node reflects movement ofthe ID node away from the fixed location and (b) the at least oneauthorized released node does not include the ID node associated withthe inventory item.

5. The method of embodiment 1, wherein the master node is associatedwith a storage facility maintaining an inventory level of items, whereinthe current inventory level of items reflects maintaining the inventoryitem at the storage facility.

6. The method of embodiment 5 further comprising the step of updatinginventory control information related to the inventory level of itemswhen the detected movement of the ID node reflects movement of the IDnode away from the fixed location and the ID node is authorized to leavethe storage facility consistent with the release information.

7. The method of embodiment 6 further comprising the step oftransmitting the updated inventory control information to the inventorycontrol server.

8. The method of embodiment 5, wherein the generating step furthercomprises generating, by the master node, the pickup notification forthe inventory item when (a) the master node detects a location of the IDnode as being beyond a threshold distance away from the fixed locationof the master node and (b) the release information received by themaster node does not authorize the ID node to leave the storagefacility.

9. The method of embodiment 1 further comprising the step of providingthe pickup notification on a user interface of the master node, thepickup notification indicating the inventory item has been improperlymoved.

10. The method of embodiment 1, wherein the pickup notification furtherindicating the inventory item has improperly been removed from a storagefacility associated with the master node at the first location.

11. The method of embodiment 1 further comprising the step oftransmitting, by the master node to the inventory control server, analert related to the pickup notification, wherein the alert indicatingthe inventory item has been improperly moved.

12. The method of embodiment 11, wherein the alert further providing acorrective action relative to the detected movement of the ID noderelative to the fixed location.

13. The method of embodiment 1 further comprising the step oftransmitting, by the master node to a second node device, an alertrelated to the pickup notification, wherein the alert indicating theinventory item has been improperly moved.

14. A master node apparatus for generating a pickup notification relatedto an inventory item, the master node comprising: a node processingunit; a node memory storage coupled to the node processing unit, thenode memory storage maintaining pickup notification code for executionby the node processing unit; a first communication interface coupled tothe node processing unit and operative to communicate with an ID nodeassociated with the inventory item; a second communication interfacecoupled to the node processing unit and operative to communicate with aninventory control server; and

wherein the node processing unit, when executing the deliverynotification code maintained on the node memory storage, is operative tocommunicate with the ID node over the first communication interface tomonitor a location of the ID node associated with the inventory item,receive release information from the inventory control server over thesecond communication interface and store the received releaseinformation in the node memory storage, detect movement of the ID noderelative to a fixed location of the master node apparatus, and generatethe pickup notification for the inventory item based upon the releaseinformation and the detected movement of the ID node.

15. The master node apparatus of embodiment 14, wherein the releaseinformation identifies a category for inventory release; and whereinnode processing unit is further operative to generate the pickupnotification when (a) the detected movement of the ID node reflectsmovement of the ID node away from the fixed location and (b) thecategory for inventory release does not correspond to the inventoryitem.

16. The master node apparatus of embodiment 14, wherein the releaseinformation identifies a category for inventory release; and wherein thenode processing unit is further operative to generate the pickupnotification for the inventory item when (a) the detected movement ofthe ID node reflects movement of the ID node away from the fixedlocation and (b) the category for inventory release does not correspondto the ID node associated with the inventory item.

17. The master node apparatus of embodiment 14, wherein the releaseinformation comprises at least one authorized released node; and whereinthe node processing unit is further operative to generate the pickupnotification for the inventory item when (a) the detected movement ofthe ID node reflects movement of the ID node away from the fixedlocation and (b) the at least one authorized released node does notinclude the ID node associated with the inventory item.

18. The master node apparatus of embodiment 14, wherein the inventoryitem is maintained as part of an inventory of a storage facility, thestorage facility being associated with the master node apparatus.

19. The master node apparatus of embodiment 18, wherein the nodeprocessing unit is further operative to update inventory controlinformation maintained on the node memory storage, the inventory controlinformation related to a level of the inventory, the updated inventorycontrol information reflecting a revised level of the inventory when thedetected movement of the ID node reflects movement of the ID node awayfrom the fixed location and the ID node is authorized to leave thestorage facility consistent with the release information.

20. The master node apparatus of embodiment 19, wherein the nodeprocessing unit is further operative to cause the second communicationinterface to transmit the updated inventory control information to theinventory control server.

21. The master node apparatus of embodiment 18, wherein node processingunit is operative to generate the pickup notification when (a) themaster node detects the movement of the ID node is beyond a thresholddistance away from the fixed location of the master node and (b) therelease information received from the inventory control server does notauthorize the ID node to leave the storage facility.

22. The master node apparatus of embodiment 14 further comprising a userinterface disposed on the master node apparatus and coupled to the nodeprocessing unit; and wherein the node processing unit being furtheroperative to provide the pickup notification on the user interface ofthe master node, the pickup notification indicating the inventory itemhas been improperly moved.

23. The master node apparatus of embodiment 14, wherein the pickupnotification further indicating the inventory item has improperly beenremoved from a storage facility associated with the master node at thefirst location.

24. The master node apparatus of embodiment 14, wherein the nodeprocessing unit is further operative to cause the second communicationinterface to transmit an alert related to the pickup notification to theinventory control server, wherein the alert indicating the inventoryitem has been improperly moved.

25. The master node apparatus of embodiment 24, wherein the alertfurther providing a corrective action relative to the detected movementof the ID node relative to the fixed location.

26. The master node apparatus of embodiment 14, wherein the nodeprocessing unit is further operative to cause the first communicationinterface to transmit an alert related to the pickup notification to asecond device, wherein the alert indicating the inventory item has beenimproperly moved.

27. A system for generating a pickup notification related to aninventory item, the system comprising: an inventory control servermaintaining release information; and a master node associated with afixed location,

the master node comprising a node processing unit; a node memory storagecoupled to the node processing unit, the node memory storage maintainingpickup notification code for execution by the node processing unit; afirst communication interface coupled to the node processing unit andoperative to communicate with an ID node associated with the inventoryitem; a second communication interface coupled to the node processingunit and operative to communicate with the inventory control server; and

wherein the node processing unit, when executing the deliverynotification code maintained on the node memory storage, is operative tocommunicate with the ID node over the first communication interface tomonitor a location of the ID node associated with the inventory item,receive release information from the inventory control server over thesecond communication interface and store the received releaseinformation in the node memory storage, detect movement of the ID noderelative to a fixed location of the master node apparatus, generate thepickup notification for the inventory item based upon the releaseinformation and the detected movement of the ID node, cause the secondcommunication interface to transmit a first alert to the inventorycontrol server based upon the generated pickup notification, wherein thefirst alert indicating the inventory item has been improperly moved, andcause the second communication interface to transmit a second alert tothe inventory control server based upon the generated pickupnotification, wherein the second alert indicating the inventory item hasbeen properly moved; and

wherein the inventory control server is operative to transmit therelease information to the second communication interface, and receiveat least one of the first alert and the second alert from the masternode.

28. The system of embodiment 27, wherein the inventory item ismaintained as part of an inventory of a storage facility, the storagefacility being associated with the master node apparatus.

29. The system of embodiment 28, wherein the node processing unit of themaster node is further operative to update inventory control informationmaintained on the node memory storage, the inventory control informationrelated to a level of the inventory, the updated inventory controlinformation reflecting a revised level of the inventory when thedetected movement of the ID node reflects movement of the ID node awayfrom the fixed location and the ID node is authorized to leave thestorage facility consistent with the release information.

30. The system of embodiment 29, wherein the node processing unit of themaster node is further operative to cause the second communicationinterface to transmit the updated inventory control information to theinventory control server; and wherein the inventory control server isoperative to receive the updated inventory control information from themaster node.

Further Embodiment G Enhanced Delivery Management Methods, Apparatus,and Systems for a Shipped Item Using a Mobile Node-Enabled LogisticsReceptacle

1. A method for enhanced delivery management of an item using a mobilenode-enabled logistics receptacle, the method comprising: identifying,by the mobile node-enabled logistics receptacle, an intended deliverylocation associated with the item; detecting a current location of themobile node-enabled logistics receptacle; and selectively releasing, bythe mobile node-enabled logistics receptacle, the item from the mobilenode-enabled logistics receptacle based upon the detected currentlocation of the mobile node-enabled logistics receptacle and theidentified intended delivery location.

2. The method of embodiment 1, wherein the identifying step furthercomprising: detecting, by the mobile node-enabled logistics receptacle,a signal broadcast from a node associated with the item; accessing, bythe mobile node-enabled logistics receptacle, shipping informationwithin the detected signal, wherein the shipping information is relatedto the item; and identifying the intended delivery location from theshipping information.

3. The method of embodiment 2 further comprising establishing a secureconnection to the node associated with the item.

4. The method of embodiment 3, wherein the secure connection comprisesan encrypted exchange of the shipping information.

5. The method of embodiment 1, wherein the selectively releasing stepfurther comprises: comparing, by the mobile node-enabled logisticsreceptacle, the detected current location of the mobile node-enabledlogistics receptacle to the identified intended delivery location; andreleasing, by the mobile node-enabled logistics receptacle, the itemfrom a storage area within the mobile node-enabled logistics receptaclebased upon the comparison of the detected current location of the mobilenode-enabled logistics receptacle to the identified intended deliverylocation.

6. The method of embodiment 5, wherein the releasing step furthercomprises releasing, by the mobile node-enabled logistics receptacle,the item from the storage area when the comparison of the detectedcurrent location of the mobile node-enabled logistics receptacle to theidentified intended delivery location indicates the detected currentlocation of the mobile node-enabled logistics receptacle is within athreshold proximity area associated with the intended delivery location.

7. The method of embodiment 1, wherein the selectively releasing stepfurther comprises: establishing a validation connection with a nodeassociated with the intended delivery location to authorize releasingthe item; and releasing, by the mobile node-enabled logisticsreceptacle, the item from within the mobile node-enabled logisticsreceptacle based upon the detected current location of the mobilenode-enabled logistics receptacle and the location of the mobile useraccess device and after establishing the validation connection.

8. The method of embodiment 7, wherein the step of establishing thevalidation connection further comprises establishing a secure validationconnection with the node associated with the intended delivery location.

9. The method of embodiment 7, wherein the validation connectioncomprises at least one of a prompted connection with the node associatedwith the intended delivery location and a preauthorized connectionbetween the mobile node-enabled logistics receptacle and the nodeassociated with the intended delivery location.

10. The method of embodiment 1, wherein the selectively releasing stepfurther comprises: determining, by the mobile node-enabled logisticsreceptacle, a proximity distance between the detected current locationof the mobile node-enabled logistics receptacle and the identifiedintended delivery location; and actuating, by the mobile node-enabledlogistics receptacle, a lockable opening to a storage area on the mobilenode-enabled logistics receptacle to release the item based upon thedetermined proximity distance.

11. The method of embodiment 10, wherein the actuating step furtherautomatically unlocking, by the mobile node-enabled logisticsreceptacle, the lockable opening to a storage area on the mobilenode-enabled logistics receptacle to release the item when thedetermined proximity distance is less than a threshold proximitydistance.

12. The method of embodiment 11, wherein the step of automaticallyunlocking further comprises identifying a portion of the storage areathat maintains the item; and automatically, when the determinedproximity distance is less than the threshold proximity distance,unlocking an access opening to the identified portion of the storagearea to provide delivery access to the item.

13. The method of embodiment 12, further comprising maintaining a lockedstate for a remaining part of the storage area that is not identified asthe portion of the storage area that maintains the item.

14. The method of embodiment 1 further comprising the step of receiving,by the mobile node-enabled logistics receptacle, a delivery locationsignal broadcast from a node associated with the intended deliverylocation; and wherein the selectively releasing step comprisesautomatically unlocking, by the mobile node-enabled logisticsreceptacle, an opening to a storage area maintaining the item afterreceiving the delivery location signal.

15. The method of embodiment 14 further comprising establishing a secureconnection to the node associated with the intended delivery location.

16. The method of embodiment 14, wherein the step of automaticallyunlocking further comprises: identifying a portion of the storage areathat maintains the item; and automatically, after receiving the deliverylocation signal, unlocking an access opening to the identified portionof the storage area to provide delivery access to the item.

17. The method of embodiment 16 further comprising maintaining a lockedstate for a remaining part of the storage area that is not identified asthe portion of the storage area that maintains the item.

18. The method of embodiment 1 further comprising generating an alertrelated to releasing the item from the mobile node-enabled logisticsreceptacle.

19. The method of embodiment 1, wherein the intended delivery locationcomprises a recipient location.

20. The method of embodiment 19, wherein the recipient locationcomprises a location of a mobile user access device operative tofunction as a master node, wherein the mobile user access device isassociated with a recipient for the item.

21. The method of embodiment 20, wherein the selectively releasing stepfurther comprises: establishing, by the mobile node-enabled logisticsreceptacle, a validation connection with the mobile user access deviceto authorize releasing the item; and releasing, by the mobilenode-enabled logistics receptacle, the item from within the mobilenode-enabled logistics receptacle based upon the detected currentlocation of the mobile node-enabled logistics receptacle and thelocation of the mobile user access device and after successfullyestablishing the validation connection.

22. The method of embodiment 21, wherein the validation connectionfurther comprises a secure validation connection with the mobile useraccess device.

23. The method of embodiment 21, wherein the establishing step furthercomprises establishing an active prompted connection between the mobilenode-enabled logistics receptacle and the mobile user access device toreceive a prompted authorization release acknowledgement from the mobileuser access device in order to authorize releasing the item.

24. The method of embodiment 21, wherein the establishing step furthercomprises establishing a preauthorized connection between the mobilenode-enabled logistics receptacle and the mobile user access device toautomatically authorize releasing the item.

25. The method of embodiment 24, wherein establishing the preauthorizedconnection further comprises establishing the preauthorized connectionbetween the mobile node-enabled logistics receptacle and the mobile useraccess device to automatically authorize releasing the item based upon apreviously authorized release validation condition that occursautomatically when the mobile node-enabled logistics receptacle detectsa signal broadcast as an advertising signal from the mobile user accessdevice related to the recipient of the item.

26. The method of embodiment 1, wherein the step of selectivelyreleasing the item further comprises selectively articulating a lockableelement on the mobile node-enabled logistics receptacle to cause theitem to separate from the mobile node-enabled logistics receptacle.

27. The method of embodiment 26, wherein the lockable element comprisesat least one from the group consisting of one or more doors supportingthe item while in a closed state but allowing the item to transfer fromthe mobile node-enabled receptacle in an open state, and one or morearticulating grips holding the item in a secure configuration in theclosed state but releasing the item from the secure configuration in theopen state.

28. A mobile node-enabled logistics receptacle apparatus having enhanceddelivery release control related to an item, the apparatus comprising:

a logistics receptacle comprising a storage area for maintaining theitem, and a lockable opening through which the item and a nodeassociated with the item can pass into the storage area;

a node coupled to the logistics receptacle, the node further comprisinga node processing unit, a node memory storage coupled to the nodeprocessing unit, the node memory storage maintaining delivery releasecontrol code for execution by the node processing unit and shippinginformation related to the item, location circuitry coupled to the nodeprocessing unit, the location circuitry being operative to detect alocation of the mobile node-enabled logistics receptacle apparatus, anactuator operatively coupled to the lockable opening and controlled bythe node processing unit, the actuator controlling access to the storagearea by controlling a state of the lockable opening, and a communicationinterface coupled to the node processing unit and operative to access awireless communication path; and

wherein the node processing unit, when executing the delivery releasecontrol code maintained on the node memory storage, is operative toidentify an intended delivery location associated with the item from theshipping information stored in the memory, cause the location circuitryto detect a current location of the mobile node-enabled logisticsreceptacle apparatus, and selectively cause the actuator to change thestate of the lockable opening to an open state to provide deliveryaccess to the item within the storage area based upon the detectedcurrent location of the mobile node-enabled logistics receptacleapparatus and the identified intended delivery location.

29. The mobile node-enabled logistics receptacle apparatus of embodiment28, wherein the communication interface is operative to detect a signalfrom the node associated with the item; and wherein the node processingunit is further operative to identify the intended delivery location bybeing operative to receive at least a portion of the detected signalfrom the communication interface; access shipping information within theportion of the detected signal, wherein the shipping information isrelated to the item; and identify the intended delivery location fromthe shipping information.

30. The mobile node-enabled logistics receptacle apparatus of embodiment28, wherein the node processing unit is further operative toestablishing a secure connection over the communication interface to thenode associated with the item.

31. The mobile node-enabled logistics receptacle apparatus of embodiment30, wherein the secure connection comprises an encrypted exchange of theshipping information.

32. The mobile node-enabled logistics receptacle apparatus of embodiment28, wherein the node processing unit is operative to selectively causethe actuator to change to the open state by being operative to comparethe detected current location of the mobile node-enabled logisticsreceptacle apparatus to the identified intended delivery location; andselectively cause the actuator to change the state of the lockableopening to the open state based upon based upon the comparison of thedetected current location of the mobile node-enabled logisticsreceptacle apparatus to the identified intended delivery location.

33. The mobile node-enabled logistics receptacle apparatus of embodiment32, wherein the node processing unit is further operative to selectivelycause the actuator to change to the open state when the comparisonindicates the detected current location is within a threshold proximityarea associated with the intended delivery location

34. The mobile node-enabled logistics receptacle apparatus of embodiment28, wherein the node processing unit is operative to the selectivelycause the actuator to change the state of the lockable opening to theopen state by being further operative to: establish a validationconnection, using the communication interface, with a node associatedwith the intended delivery location to authorize releasing the item; andcause the actuator to change the state of the lockable opening to theopen state based upon the detected current location of the mobilenode-enabled logistics receptacle and the location of the mobile useraccess device and after successfully establishing the validationconnection.

35. The mobile node-enabled logistics receptacle apparatus of embodiment34, wherein the validation connection further comprises a securevalidation connection with the node associated with the intendeddelivery location.

36. The mobile node-enabled logistics receptacle apparatus of embodiment34, wherein the validation connection comprises at least one of aprompted connection with the node associated with the intended deliverylocation and a preauthorized connection between the mobile node-enabledlogistics receptacle and the node associated with the intended deliverylocation.

37. The mobile node-enabled logistics receptacle apparatus of embodiment28, wherein the node processing unit is operative to selectively causethe actuator to change the state of the lockable opening to the openstate by being further operative to cause the actuator to unlock thelockable opening based upon a proximity distance between the detectedcurrent location of the mobile node-enabled logistics receptacleapparatus and the identified intended delivery location.

38. The mobile node-enabled logistics receptacle apparatus of embodiment37, wherein the node processing unit is operative to cause the actuatorto unlock the lockable opening by being further operative to cause theactuator to automatically unlock the lockable opening to the storagearea when the determined proximity distance is less than a thresholdproximity distance.

39. The mobile node-enabled logistics receptacle apparatus of embodiment28, wherein the node processing unit is further operative to receive adelivery location signal from the communication interface, the deliverylocation signal being broadcast from a node associated with the intendeddelivery location; and wherein the node processing unit is operative toselectively cause the actuator to change the state of the lockableopening to the open state by being further operative to cause theactuator to automatically unlock the lockable opening after receivingthe delivery location signal.

40. The mobile node-enabled logistics receptacle apparatus of embodiment39, wherein the node processing unit is operative to receive thedelivery location signal by establishing a secure connection over thecommunication interface to the node associated with the intendeddelivery location.

41. The mobile node-enabled logistics receptacle apparatus of embodiment39, wherein the delivery location signal is broadcast from a mobile nodeassociated with the intended delivery location.

42. The mobile node-enabled logistics receptacle apparatus of embodiment39, wherein the delivery location signal is broadcast from a fixed nodeassociated with the intended delivery location.

43. The mobile node-enabled logistics receptacle apparatus of embodiment28, wherein the node processing unit is further operative to generate analert related to release of the item from the mobile node-enabledlogistics receptacle.

44. The mobile node-enabled logistics receptacle apparatus of embodiment43, wherein the node processing unit is further operative to cause thecommunication interface to transmit the alert to a node associated withthe intended delivery location.

45. The mobile node-enabled logistics receptacle apparatus of embodiment43, wherein the node further comprises a user interface; and wherein thenode processing unit is further operative to generate the alert by beingoperative to display the generated alert with the user interface.

46. The mobile node-enabled logistics receptacle apparatus of embodiment45, wherein the user interface comprises a speaker; and wherein the nodeprocessing unit is further operative to generate the alert by beingoperative to play an auditory alert with the speaker.

47. The mobile node-enabled logistics receptacle apparatus of embodiment28, wherein the intended delivery location comprises a recipient relatedlocation.

48. The mobile node-enabled logistics receptacle apparatus of embodiment47, wherein the recipient related location comprises a location of amobile user access device identified in the shipping information,wherein the mobile user access device is operative to function as amaster node and associated with a recipient for the item.

49. The mobile node-enabled logistics receptacle apparatus of embodiment48, wherein the node processing unit is operative to the selectivelycause the actuator to change the state of the lockable opening to theopen state by being further operative to: establish a validationconnection, using the communication interface, with the mobile useraccess device to authorize releasing the item; and cause the actuator tochange the state of the lockable opening to the open state based uponthe detected current location of the mobile node-enabled logisticsreceptacle and the location of the mobile user access device and aftersuccessfully establishing the validation connection.

50. The mobile node-enabled logistics receptacle apparatus of embodiment49, wherein the validation connection further comprises a securevalidation connection, using the communication interface, with themobile user access device.

51. The mobile node-enabled logistics receptacle apparatus of embodiment49, wherein the node processing unit is operative to establish thevalidation connection using the communication interface by being furtheroperative to establish an active prompted connection between the mobilenode-enabled logistics receptacle and the mobile user access device overthe wireless communication path to receive a prompted authorizationrelease acknowledgement from the mobile user access device in order toauthorize releasing the item.

52. The mobile node-enabled logistics receptacle apparatus of embodiment49, wherein the node processing unit is operative to establish thevalidation connection using the communication interface by being furtheroperative to establish a preauthorized connection between the mobilenode-enabled logistics receptacle and the mobile user access device overthe wireless communication path to automatically authorize releasing theitem.

53. The mobile node-enabled logistics receptacle apparatus of embodiment52, wherein the node processing unit is further operative to establishthe preauthorized connection between the mobile node-enabled logisticsreceptacle and the mobile user access device to automatically authorizereleasing the item based upon a previously authorized release validationcondition that occurs automatically when the mobile node-enabledlogistics receptacle detects a signal broadcast as an advertising signalfrom the mobile user access device related to the recipient of the item.

54. A node-enabled logistics vehicular system having enhanced deliveryrelease control related to an item, the system comprising: a logisticsvehicle further comprising a first storage area for maintaining theitem, and a first lockable opening through which the item and a noderelated to the item can pass into the storage area; a master nodedisposed on the logistics vehicle, the master node further comprising anode processing unit, a node memory storage coupled to the nodeprocessing unit, the node memory storage maintaining delivery releasecontrol code for execution by the node processing unit and shippinginformation related to the item, location circuitry coupled to the nodeprocessing unit, the location circuitry being operative to detect alocation of the logistics vehicle, a first actuator operatively coupledto the node processing unit and the first lockable opening, the firstactuator controlling access to the first storage area by controlling astate of the first lockable opening, and a first communication interfacecoupled to the node processing unit and operative to communicate with atleast the node related to the item over a first wireless communicationpath; a second communication interface coupled to the node processingunit and operative to communicate with a server over a second wirelesscommunication path; and

wherein the node processing unit of the master node, when executing thedelivery release control code maintained on the node memory storage, isoperative to identify an intended delivery location associated with theitem from the shipping information stored in the memory, cause thelocation circuitry to detect a current location of the logisticsvehicle, and selectively cause the first actuator to change the state ofthe first lockable opening to an open state to provide delivery accessto the item within the first storage area based upon the detectedcurrent location of the logistics vehicle and the identified intendeddelivery location.

55. The node-enabled logistics vehicular system of embodiment 54,wherein the first communication interface is further operative to detecta signal broadcast from the node related to the item; and wherein thenode processing unit is further operative to identify the intendeddelivery location by being operative to identify the intended deliverylocation based upon a portion of the detected signal, wherein theportion of the detected signal includes broadcast data indicating theshipping information for the item.

56. The node-enabled logistics vehicular system of embodiment 54,wherein the node processing unit is further operative to establishing asecure connection over the first communication interface to the noderelated to the item.

57. The node-enabled logistics vehicular system of embodiment 56,wherein the secure connection comprises an encrypted exchange of theshipping information.

58. The node-enabled logistics vehicular system of embodiment 54,wherein the node processing unit is further operative to selectivelycause the first actuator to change to the open state when the detectedcurrent location of the logistics vehicle is within a proximity servicearea associated with the intended delivery location.

59. The node-enabled logistics vehicular system of embodiment 54,wherein the node processing unit is operative to selectively cause thefirst actuator to change the state of the first lockable opening to theopen state by being further operative to cause the first actuator tounlock the first lockable opening when a proximity distance between thedetected current location of the logistics vehicle and the identifiedintended delivery location is less than a threshold proximity distance.

60. The node-enabled logistics vehicular system of embodiment 54,wherein the node processing unit is further operative to receive adelivery location signal from the first communication interface or fromthe second communication interface, the delivery location signal beingbroadcast from a node associated with the intended delivery location;and wherein the node processing unit is operative to selectively causethe first actuator to change the state of the first lockable opening tothe open state by being further operative to cause the first actuator toautomatically unlock the first lockable opening after receiving thedelivery location signal.

61. The node-enabled logistics vehicular system of embodiment 60,wherein the node processing unit is further operative to establish asecure connection to the node associated with the intended deliverylocation as part of receiving the delivery location signal.

62. The node-enabled logistics vehicular system of embodiment 60,wherein the delivery location signal is broadcast from a mobile nodeassociated with the intended delivery location.

63. The node-enabled logistics vehicular system of embodiment 60,wherein the delivery location signal is broadcast from a fixed nodeassociated with the intended delivery location.

64. The node-enabled logistics vehicular system of embodiment 54,wherein the node processing unit is further operative to cause thesecond communication interface to transmit an alert to a node associatedwith the intended delivery location, wherein the alert relates to thedelivery access to the item based upon the open state of the firstlockable opening.

65. The node-enabled logistics vehicular system of embodiment 54,wherein the logistics vehicle further comprises a second storage areaand a second lockable opening through which to access the second storagearea; wherein the master node further comprising a second actuatoroperatively coupled to the second lockable opening and controlled by thenode processing unit, the second actuator controlling access to thesecond storage area by controlling a state of the second lockableopening; and wherein the node processing unit of the master node isfurther operative to selectively cause the first actuator to change thestate of the first lockable opening to the open state to providedelivery access to the item within the first storage area based upon thedetected current location of the logistics vehicle and the identifiedintended delivery location while causing the second actuator to maintainthe state of the second lockable opening in a closed state to preventaccess to what is stored within the second storage area.

What is claimed is:
 1. An improved location-based system for generatinga corrective pickup notification related to an item being shipped basedupon an intended pickup master node, the system comprising: a logisticsserver that maintains a copy of shipping information related to the itembeing shipped and an ID node associated with the item being shipped; anda mobile master node in communication with the logistics server and incommunication with the ID node associated with the item being shipped,the mobile master node comprising, a node processing unit, a node memorystorage coupled to the node processing unit of the mobile master node,the node memory storage maintaining delivery notification code forexecution by the node processing unit, location circuitry coupled to thenode processing unit of the mobile master node, the location circuitrybeing operative to detect a current location of the mobile master node,a first communication interface coupled to the node processing unit andoperative to access a first wireless communication path connecting themobile master node with at least the ID node associated with the itembeing shipped, and a second communication interface coupled to the nodeprocessing unit and operative to access a second wireless communicationpath connecting the mobile master node with the logistics server, thefirst wireless communication path being distinct from the secondwireless communication path; and wherein the node processing unit of themobile master node, when executing the delivery notification codemaintained on the node memory storage, is operative to identify alocation of the ID node associated with the item being shipped;determine whether the identified location of the ID node and thedetected current location of the mobile master node remain within athreshold distance from each other to indicate the item is accompanyingthe mobile master node as the mobile master node moves from a firstlocation to a second location; receive shipping information related tothe item from the logistics server; identify the intended pickup masternode from the received shipping information; automatically sense anadverse pickup condition related to the item based upon the identifiedintended pickup master node and whether the location of the ID node andthe detected location of the mobile master node indicates the item isaccompanying the mobile master node; and generate the corrective pickupnotification based upon the adverse pickup condition sensed.
 2. Thesystem of claim 1, wherein the node processing unit of the mobile masternode is further operative to automatically sense the adverse pickupcondition as when the identified intended pickup master node does notcorrespond to the mobile master node and the identified location of theID node indicates the item is accompanying the mobile master node. 3.The system of claim 1, wherein the mobile master node further comprisesa user interface coupled to the node processing unit; and wherein thenode processing unit of the mobile master node is operative to generatethe corrective pickup notification as a prompt to be displayed on theuser interface of the mobile master node, the prompt being related tothe adverse pickup condition.
 4. The system of claim 1, wherein theprompt further comprises electronic feedback on the user interface ofthe mobile master node.
 5. The system of claim 4, wherein the electronicfeedback includes at least a displayed instruction on the user interfacenot to deliver the item based upon the sensed adverse pickup condition.6. The system of claim 4, wherein the electronic feedback includes atleast a displayed instruction on the user interface to alter a currentdirection of movement based upon the sensed adverse pickup condition. 7.The system of claim 6, wherein the displayed instruction to alter thecurrent direction of movement comprises an instruction shown on the userinterface of the mobile master node for the operator of the mobilemaster node to move to a specified location.
 8. The system of claim 7,wherein the specified location comprises a prior location of the mobilemaster node.
 9. The system of claim 1, wherein the mobile master nodefurther comprises a speaker coupled to the node processing unit; andwherein the node processing unit is operative to generate the correctivepickup notification as an alert sound played through the speaker of themobile master node.
 10. A mobile master node apparatus for generating acorrective pickup notification related to an item being shipped basedupon an intended pickup master node, the mobile apparatus comprising: anode processing unit; a node memory storage coupled to the nodeprocessing unit, the node memory storage maintaining deliverynotification code for execution by the node processing unit; locationcircuitry coupled to the node processing unit, the location circuitrybeing operative to detect a current location of the mobile master nodeapparatus; a communication interface coupled to the node processing unitand operative to access a first wireless communication path connectingthe mobile master node apparatus with at least an ID node associatedwith the item being shipped; and wherein the node processing unit, whenexecuting the delivery notification code maintained on the node memorystorage, is operative to identify a location of the ID node associatedwith the item; determine whether the identified location of the ID nodeand the detected current location of the mobile master node apparatusindicates the item is accompanying the mobile master node apparatus asthe mobile master node apparatus moves from a first location to a secondlocation; receive shipping information related to the item; identify theintended pickup master node from the shipping information; automaticallysense an adverse pickup condition related to the item based upon theidentified intended pickup master node and whether the location of theID node indicates the item is accompanying the mobile master nodeapparatus; and generate the corrective pickup notification based uponthe adverse pickup condition sensed.
 11. The mobile master nodeapparatus of claim 10, wherein the node processing unit is furtheroperative to automatically sense the adverse pickup condition as whenthe identified intended pickup master node does not correspond to themobile master node apparatus and the identified location of the ID nodeindicates the item is accompanying the mobile master node apparatus. 12.The mobile master node apparatus of claim 10, wherein the shippinginformation is received from the ID node over a secure connectionbetween the ID node and the mobile master node apparatus over the firstwireless communication path.
 13. The mobile master node apparatus ofclaim 10, wherein the communication interface is further operative toaccess a second wireless communication path distinct from the firstwireless communication path, the second wireless communication pathconnecting the mobile master node apparatus with a server; and whereinthe shipping information is received from the server over a secureconnection between the server and the mobile master node apparatus overthe second wireless communication path.
 14. The mobile master nodeapparatus of claim 10 further comprising a user interface coupled to thenode processing unit; and wherein the node processing unit is operativeto generate the corrective pickup notification as a prompt to bedisplayed on the user interface of the mobile master node apparatus, theprompt being related to the adverse pickup condition.
 15. The mobilemaster node apparatus of claim 14, wherein the prompt further compriseselectronic feedback on the user interface of the mobile master node. 16.The mobile master node apparatus of claim 15, wherein the electronicfeedback includes at least a displayed instruction on the user interfacenot to deliver the item based upon the sensed adverse pickup condition.17. The mobile master node apparatus of claim 16, wherein the electronicfeedback includes at least a displayed instruction on the user interfaceto alter a current direction of movement based upon the sensed adversepickup condition.
 18. The mobile master node apparatus of claim 17,wherein the displayed instruction to alter the current direction ofmovement comprises an instruction shown on the user interface of themobile master node apparatus for the operator of the mobile master nodeapparatus to move to a specified location.
 19. The mobile master nodeapparatus of claim 18, wherein the specified location comprises a priorlocation of the mobile master node apparatus.
 20. The mobile master nodeapparatus of claim 10 further comprising a speaker coupled to the nodeprocessing unit; and wherein the node processing unit is operative togenerate the corrective pickup notification as an alert sound playedthrough the speaker of the mobile master node apparatus.
 21. An improvedlocation-based method for generating a corrective pickup notificationrelated to an item being shipped based upon an intended pickup masternode, the method comprising: identifying, by a mobile master node, alocation of an ID node associated with the item; determining, by themobile master node, whether the location of the ID node indicates theitem is accompanying the mobile master node as the mobile master nodemoves from a first location to a second location; receiving, by themobile master node, shipping information related to the item;identifying, by the mobile master node, the intended pickup master nodefrom the shipping information; automatically sensing, by the mobilemaster node, an adverse pickup condition related to the item based uponthe intended pickup master node and whether the location of the ID nodeindicates the item is accompanying the mobile master node; andgenerating, by the mobile master node, the corrective pickupnotification based upon the adverse pickup condition sensed.
 22. Themethod of claim 21, wherein the step of determining further comprises:detecting, by location circuitry on the mobile master node, a locationof the mobile master node; and comparing the location of the mobilemaster node to the location of the ID node as the mobile master nodemoves from the first location to the second location to determinewhether the item is accompanying the mobile master node.
 23. The methodof claim 21, wherein the step of automatically sensing further comprisesautomatically sensing, by the mobile master node, the adverse pickupcondition related to the item when the intended pickup master node doesnot correspond to the mobile master node and the location of the ID nodeindicates the item is accompanying the mobile master node.
 24. Themethod of claim 21, wherein the shipping information is received fromthe ID node over a secure connection between the ID node and the mobilemaster node.
 25. The method of claim 21, wherein the shippinginformation is received from a server over a secure connection betweenthe server and the mobile master node.
 26. The method of claim 21,wherein the step of generating the corrective pickup notificationfurther comprises generating a prompt on the mobile master node, theprompt being related to the adverse pickup condition.
 27. The method ofclaim 26, wherein the prompt further comprises an alert sound generatedby the mobile master node.
 28. The method of claim 26, wherein theprompt further comprises electronic feedback on a user interface of themobile master node.
 29. The method of claim 28, wherein the electronicfeedback includes at least a displayed instruction not to deliver theitem based upon the sensed adverse pickup condition.
 30. The method ofclaim 28, wherein the electronic feedback includes at least a displayedinstruction to alter a current direction of movement based upon thesensed adverse pickup condition.
 31. The method of claim 30, wherein thedisplayed instruction to alter the current direction of movementcomprises an instruction to move to a specified location.
 32. The methodof claim 31, wherein the specified location comprises a prior locationof the mobile master node.